1
23.7 Legacy Series / WAN connectivity loss after modem was powered off
« on: August 31, 2023, 01:50:47 pm »
Hi
The Setup:
OPNSense (VM) -> ESX Host -> Switch (Cisco) -> XGS-PON Bridge (Nokia) -> WAN FTTH
Everything here is powered by UPS.
Problem:
As of some re-wireing stuff I've disconnected my XGS-PON Bridge Power & Fiber. I've replaced it and then reconnected it again.
After re-wireing was finished I had no WAN connectivity at all. So I logged in to my opnsense FW to check whats happened.
I saw, that the WAN interface was stuck without IPv4 address with just the IPv6 address assigned.
But no connectivity at all. So I opend "Interfaces -> Overview -> WAN" and klicked "Release/Renew". After that everything was working again.
I assume that the problem is, as the WAN link never went really down in the view of opnsense. As it runs as a VM, the NIC was never disconnected. So may it never really noticed that the link was down and a new DHCP request is needed.
Any Idea how this could be solved propperly?
The Setup:
OPNSense (VM) -> ESX Host -> Switch (Cisco) -> XGS-PON Bridge (Nokia) -> WAN FTTH
Everything here is powered by UPS.
Problem:
As of some re-wireing stuff I've disconnected my XGS-PON Bridge Power & Fiber. I've replaced it and then reconnected it again.
After re-wireing was finished I had no WAN connectivity at all. So I logged in to my opnsense FW to check whats happened.
I saw, that the WAN interface was stuck without IPv4 address with just the IPv6 address assigned.
But no connectivity at all. So I opend "Interfaces -> Overview -> WAN" and klicked "Release/Renew". After that everything was working again.
I assume that the problem is, as the WAN link never went really down in the view of opnsense. As it runs as a VM, the NIC was never disconnected. So may it never really noticed that the link was down and a new DHCP request is needed.
Any Idea how this could be solved propperly?