Everything is messed up after a power outage
-
I've had a pfsense box for probably over 5 years without many problems but when i woke up today after a power outage (unrelated but my pc bios settings got wiped too), my internet would not work at all. The gateway status just said pending and would not connect to the internet at all.
I googled for a while trying to find the problem and eventually I tried just switching the interfaces, so I switched the cables in the 2 network cards for lan and wan and reassigned interfaces and it started working perfectly or so I thought, later that night I tried using my android tablet which can only use wifi and it would not connect, neither does my iphone. If I switch the interfaces back then they can connect but will not have internet obviously. I can see in the system logs that the dhcp server is doing requests and such with them but they keep saying ip configuration errors. So at least I can duplicate the problem I guess. Working fine for my pc with an ethernet cable but none of my wifi devices work now depending on which card is the wan interface and which is lan. My setup is basically a motorola modem, xfinity internet, pfsense box, a switch and a wireless router.
I absolutely give up, why did this happen after a power outage, I didn't change any settings! If anyone smarter than me can figure this out I would be very grateful.
-
@captain3xtreme said in Everything is messed up after a power outage:
(unrelated but my pc bios settings got wiped too)
It's time to locate that battery on the MB. Change it.
@captain3xtreme said in Everything is messed up after a power outage:
I googled for a while trying to find the problem ....
Bill Gates learned us in the eighties what to do. Put on the device, and look at the screen, see it booting.
Most of us do not have a screen//keyboard hooked up t their router, so use the console access.
This access is more important as the GUI access, as this one only works if everything (or close) works.
And you can see it booting.
There will be no publicity, no blabla, only things that matter.Btw : pfSense, as a system/OS, is no different as any other other MAC/PC/Mini/Mainframe/whatever.
Remove the power cable, put it back in, and repeat that several times. Even you recent PC Windows 10 won't boot any more.
What happens is classic : you broke the file system.
It's "CHKDSK" time. More info : the pfSense manual.In a worst case scenario, you wou will lose 10 minutes of your time : down pfSense, burn it to a stick, boot from it, do a MINIMAL LAN/WAN setup. Import your backed up single "config.xml" file, wait for it to re install all your packages (if any) and your settings, do a save reboot and you're off doing other things.
ok, maybe 15 minutes if this is your first (second actually) time.
It will be like the initial pfSense install, without the set-it-up time.Because or Phones have non-removable batteries, so they can auto-shut down the proper way, this phenomena is less known to them ... otherwise we would have seen many 'broken' non bootable phones also.
The short answer to :
@captain3xtreme said in Everything is messed up after a power outage:
I absolutely give up, why did this happen after a power outage
As said above : most probably, the file system is messed up.
Google has the answer. Use an UPS. We all do. Google, for example, invested a little over 2 billion just doing that.@captain3xtreme said in Everything is messed up after a power outage:
I can see in the system logs that the dhcp server is doing requests and such with them but they keep saying ip configuration errors.
When you set up interface with IP's etc - and apply, you are reminded on top top of the screen, in green, that you have to check for every interface, the DHCP server setup.
If the DHCP server, set up using a pool like 192.168.2.10 to 192.168.2.50 and you (changed) your LAN interface to 192.168.1.1/24, the DHCP server wouldn't work anymore.
Check it's settings. -
This is why you should use a UPS.
-
So I wasn't able to figure out exactly what the problem is because I reinstalled pfsense completely and it did the same thing but I tried using a different old pc and switched my intel network card over and now it's working again, i guess it has something to do with the other pc, no idea what though.