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?

@rbird: We were running 2.2.5 or 2.2.6. Upgraded to 2.3.4_p1.  About one week after the upgrade the ipsec tunnel started acting up. It is connected to a pfsense 2.3.1.  After 1-2 hours the vpn status shows as established but I lose ping to the remote server.  A quick disconnect/connect fixes it but I can't have this happening all the time. Thanks Roger I'm having the same exact problem on one of IPSec tunnels. IKEv1 from my pfSense 2.3.4p1 to an OpenBSD on far end. Traffic works perfectly, then at about 2 hours, all phase 2 traffic stops but the tunnel stays up. It's almost like tunnels are not getting torn down and re-built after a re-key/re-auth. If cycle the tunnel, everything comes back, then at 2 hours nothing. (oddly, all of my IKEv2 tunnels don't have this problem, all of those are pfSense > pfSense). This is a site-to-site IPSec, not a VPC. I checked for duplicate routes, and there aren't any. I'm not seeing anything logs pointing to any clues as to why this is happening. I thought this might be related to this issue: https://forum.pfsense.org/index.php?topic=135557.0 However we're not using OpenBGP (it's not even installed) and we don't have any tunnels to VPC. Neither of us are seeing any logs on either side giving us an idea as to why everything would work fine then stop suddenly around the 2 hour mark. Any assist as to how to troubleshoot this would be great. Thank you.

@dbstore: If I try to download that file from a browser I receive the same error. You cannot test this with a browser, there's no A/AAAA record for that. dig srv _https._tcp.pkg.pfsense.org ; <<>> DiG 9.11.2 <<>> srv _https._tcp.pkg.pfsense.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53242 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_https._tcp.pkg.pfsense.org.  IN      SRV ;; ANSWER SECTION: _https._tcp.pkg.pfsense.org. 60 IN      SRV    10 10 443 files01.netgate.com. _https._tcp.pkg.pfsense.org. 60 IN      SRV    10 10 443 files00.netgate.com. ;; AUTHORITY SECTION: pfsense.org.            300    IN      NS      ns1.netgate.com. pfsense.org.            300    IN      NS      ns2.netgate.com. ;; Query time: 152 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sat Sep 23 12:06:26 CEST 2017 ;; MSG SIZE  rcvd: 181 https://files00.netgate.com/pfSense_v2_3_4_amd64-pfSense_v2_3_4/All/pfSense-pkg-openvpn-client-export-1.4.3.txz https://files01.netgate.com/pfSense_v2_3_4_amd64-pfSense_v2_3_4/All/pfSense-pkg-openvpn-client-export-1.4.3.txz Anyway, the file is just not there.

Mmmm….. Interesting. I wonder WTF I did then, I'm sure I didn't hallucinate ! I wish I still had the board to try it again

I see dpinger restarting a number of times, like the WAN was unplugged or some change was made. I only see one alarm there though and it's on WANv6. If there is some packet loss on WAN though that would obviously be a problem. Steve

In what slot have you installed the mSATA disk? Make sure you use the middle mSATA slot, closer to the ethernet ports. Your mSATA SSD may not be supported, what model do you have?