Are all affected PCs on the same switch?  Could be a dead/unplugged switch and not pfSense at all…  Need more details!

And just to keep an old thread endlessly alive.. Upgraded 2.3.2 to 2.3.4_1 and it took just under 4hrs. I found this thread about 30 mins into the upgrade. I used the webGUI, the platform is nanobsd, the hardware is ancient AMD BE-2350. It did give me time to cobble together a newer system based on a MSI AM1M mobo, 4GB RAM, AMD 5350 cpu. I was able to restore the nanobsd config to the new 'full' platform. I'm always using HP NC365T quad port NIC cards - I've had great luck with them. You just have to remember the top port is igb3 and the bottom is igb0. This was the office router. I have a home one I plan to upgrade via console. We've rolled out 10-15 of these to our clients. Yes, there's some kind of bug in this process, but, a big THANKS! to the pfSense team and their continued commitment.

Yeah, your upgrade did not complete… And it will not ever complete most likely until re-attempted from console (option 13) and after killing most of the services except for dnsmasq (and sshd perhaps if required for upgrade). The nanoBSD installs on Alix boxes are no longer reasonably capable of upgrading due to limited RAM, sorry.

Solved, the install was successful. I believe my confusion with the ADI images was because i read documentation indicating they were for RCC-* devices. Thank you!

@opensrcjunkie: … NIC's as opposed to the USB Gigabit ethernet which would face some speed issues with the usb... "Speed" will be the last of your problems when using USB-NIC's …. Just don't even consider them as an alternative.

I probably should have researched more, but here is a link to what I ended up doing: https://forum.pfsense.org/index.php?topic=126597.msg751156#msg751156

Sounds like upgrading showed you a disk failure.

are other devices able to get an IP address via the Ethernet ports?

Syncing a number of users can slow it down drastically. This is known and something we plan to address shortly: https://redmine.pfsense.org/issues/7469

Also have a reinstallation image for the version you are coming from available along with config backups of both nodes.

i would probably run 'pkg upgrade -f' from console/ssh and reboot. maybe stop a few services that might be consuming memory, though indeed installing fresh is also an option..

I've given an IPv4 address for WAN, and given a address for the gateway (the internal address of my router). That's all. What about private networks getting blocked?

"it would be in bridge mode so the pfsense assumes the ip publica." Then it wouldn't be routing now would it..  What what is your question?

Sounds like you are looking at the wrong console. Usually the last thing it will report is ' trying to mount root…' and then you only see system messages such as link status changes. At that point the output switches to the primary console only until bootup completes. So if you're looking at a video console check serial is vice versa. Or force the primary console to the one you are looking at: https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_with_an_alternate_console Steve

The auto created Firewall rule on the WAN interface : [image: wan2.PNG] [image: wan2.PNG_thumb]

What is the hardware spec you are running Pfsense on?