Bug #8521
closed
Fails to get WAN IP after rebooting for update
0%
Description
On one of my remote pfSense boxes, I saw an update was available. I clicked the update button in the GUI. The GUI says the update was successful and the box will reboot. I lose connection (expected) and never get connection back (not expected).
The next day, someone power cycled the box twice and that did not fix the problem. Then, they logged into the GUI from the LAN side and said that the Dashboard says the WAN interface shows "n/a" instead of an IP address. On the Status > Interfaces page, the WAN interface section says the interface is "down" and has a "Renew" button. They clicked the renew button, and immediately, the WAN gets its IP and the internet works fine.
This is the second time in a row that this has happened when I installed an update on that box. Last time was a few months ago when updating to 2.4.2, I think. This time I was updating from 2.4.2 to 2.4.3p1. I have 3 pfSense installs that use APU2 computers. Only this one has this problem. This one has APU2 firmware version 4.0.7, if that matters.
Log files attached.
Files
Updated by Jim Pingle over 4 years ago
- Category set to Interfaces
- Status changed from New to Rejected
- Priority changed from High to Normal
Old report and no recent recurrences. Lots of things in this area have changed, so most likely it's either fixed no longer relevant.