Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ProximusAl

#1
You may wish to have a read of my post from a few years ago.

https://forum.opnsense.org/index.php?topic=31705.msg153860#msg153860

The TLDR is the mlx4en doesnt play nicely with QNAP.
I ended up moving to a Netgear 10G switch instead and the mlx4en's have been solid since....
#2
I just updated to 25.1.3 and it's all fine with my cable modem. Just thought I'd let you know.
#3
I have cable and mine works ok. 

The only thing I could think, is with cable I use the "Reject Leases From" setting...maybe this has changed on your provider modem?



EDIT: I posted this too quick, I am on 25.1.2, not 25.1.3.....
#4
I always get sphincter twitch on a major upgrade, but I did 4 appliances last night all of varying configs, one IPv6 only, and it was smooth as butter.

Happy days.....
#5
I use ULA with NPTv6. Rock solid

The only downside, is client will prefer IPv4 over IPv6 (ULA).

For me that's not a downside, but actually preferred :)
#6
Since being on the 24.7 train, I notice I get these sporadic messages:

2024-08-20T18:25:11   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received   
2024-08-20T18:10:11   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received   
2024-08-20T18:04:11   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received   
2024-08-20T16:10:10   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received   
2024-08-20T16:03:10   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received   
2024-08-20T14:11:10   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received   
2024-08-20T13:13:09   Warning   dpinger   EE_DHCP 1.1.1.2: duplicate echo reply received

I am running a Dual WAN failover, and 1.1.1.2 is the monitor for my failover EE_DHCP.

Does anyone have any ideas as to what may be causing these messages?  It is a 4G connection, so perhaps related. I do not recall ever seeing these pre 24.7....

I use the same monitoring on the primary (albeit different IP), and it doesn't have any issues like this.

Thanks in advance....
#7
All I can say is it works fine for me on 24.7.1.

I use R86S with Mellanox
#8
Nope.....all my data is there over the last 3 hours since I reset RRD.

No gaps
#9
I had this on upgrade to 24.7 and 24.7.1.

Had to reset RRD data and now working again.
#10
Fixed.

Change mirror..
Reboot...
Update.

Duff UK mirror I guess
#11
root@router:~ # pkg update -f
Updating OPNsense repository catalogue...
Waiting for another process to update repository OPNsense

Seems stuck...even after reboot
#12
First thing I checked was DNS. Resolves fine via diagnostics and DNS is set under system general.

Tried changing mirror but same. Maybe change mirror, reboot, try again?

I dunno. Never seen this before
#13
Hmmm. After leaving it for a bit, it now says your packages are up to date.

Mirror not synced?
#14
I'm getting this when trying to update to 24.7.1....even after a full reboot?

Any hints?
#15
Hey Franco.....

If your in the mood for documentation :).

https://opnsense.org/about/road-map/

24.7 says Next Release, 24.1 says Latest Release :P