I recently had a failure of my UPS (battery died) during a storm event that resulted in repeated cycling of line power. During the event, I lost internet connectivity and thought it was ISP's problem -- OPNsense was up and showing an IPv6 address on the WAN interface, but no IPv4. After many hours of no internet, I investigated and found that going to Interfaces>Overview>WAN->reload resulted in a valid IPV4 address on the WAN interface and restored internet connectivity.
Again making an incorrect assumption, I figured that some problem associated with repeated power outages had resulted in a rare state that would not be repeated. WRONG. I cycled the power again, after doing a clean shutdown of OPNsense, as I replaced the battery in the UPS, and once again, no IPV4 address on the WAN interface and no internet connectivity after restart. As before, going to the Interfaces>Overview>WAN->reload step restored the WAN interface to full operation.
As I have been running on a UPS for quite a while, I had not previously experienced the power cycling fault. I have, however, done numerous reboots associated with updating OPNsense, which has not resulted in loss of WAN connectivity.
OPNsense 21.7.4-amd64
FreeBSD 12.1-RELEASE-p20-HBSD
OpenSSL 1.1.1l 24 Aug 2021
Intel(R) Atom(TM) CPU E3845 @ 1.91GHz (4 cores)
Browsing for similar problems, I see that others have experienced sim
Browsing for similar problems, I see that others have experienced similar problems associated with earlier major releases of OPNsense. Is this still an outstanding issue? Any ETA for a fix? Or is there something in settings that I should change?
Thanks in advance for help/advice.
John K.ilar problems associated with earlier major releases of OPNsense. Is this still an outstanding issue? Any ETA for a fix? Or is there something in settings that I should change?
Thanks in advance for help/advice.
John K.
I am still having this problem. I had to reboot my cable modem, and the opnsense router could not establish an IPV4 address on the WAN interface until I rebooted it.
Any suggestions on what the problem might be would be much appreciated.
Thank you,
John K.