Show Posts
1
23.7 Legacy Series / failure to route after link down
« on: January 11, 2024, 04:39:52 am »
Hi All, I'm wondering if anyone has met and discovered how to overcome my current issue.
I have OPNsense 23.7.10_1-amd64 on FreeBSD 13.2-RELEASE-p7 on a Beelink Mini PC, directly connected to my FTTP NBN box.
Power to both the NBN box and the OpnSense box is provided by a UPS without software support.
My issue is that whenever there is a power outage, OpnSense does not fully recover. The OS stays up thanks to the UPS, but the WAN link goes down and when it comes back up, OPNSense is in this state:
* From my LAN, I can ping the OpnSense box; SSH into it and access the Web UI as normal.
* Once SSH'd into OpnSense, from there I can ping and curl freely about the Internet.
* However, I cannot ping or access Internet hosts from my LAN via OpnSense. It just times out.
It is as if routing is disabled somehow. If this was a Linux box I would be checking /etc/sysctl for Ipv4 forwarding settings.
A reboot of the OpnSense box fixes the issue instantly, as does disabling and re-enabling the WAN interface.
Can anyone advise how one might go about fixing this so I don't have to manually recover each time?
I have OPNsense 23.7.10_1-amd64 on FreeBSD 13.2-RELEASE-p7 on a Beelink Mini PC, directly connected to my FTTP NBN box.
Power to both the NBN box and the OpnSense box is provided by a UPS without software support.
My issue is that whenever there is a power outage, OpnSense does not fully recover. The OS stays up thanks to the UPS, but the WAN link goes down and when it comes back up, OPNSense is in this state:
* From my LAN, I can ping the OpnSense box; SSH into it and access the Web UI as normal.
* Once SSH'd into OpnSense, from there I can ping and curl freely about the Internet.
* However, I cannot ping or access Internet hosts from my LAN via OpnSense. It just times out.
It is as if routing is disabled somehow. If this was a Linux box I would be checking /etc/sysctl for Ipv4 forwarding settings.
A reboot of the OpnSense box fixes the issue instantly, as does disabling and re-enabling the WAN interface.
Can anyone advise how one might go about fixing this so I don't have to manually recover each time?