@panini This should help in configuring your dual WAN: https://docs.netgate.com/pfsense/en/latest/recipes/high-availability-multi-wan.html?highlight=configurating%20dual%20wan Will pfSense will be doing DHCP serving to the three AP's instead of each AP? That would be the best recommendation so you could see what device is associated each IP. Some reading material here: https://docs.netgate.com/pfsense/en/latest/services/dhcp/index.html?highlight=dhcp https://docs.netgate.com/pfsense/en/latest/recipes/external-wireless-router.html?highlight=dhcp

@kevin_fndtn Get your key ready, they will reply fast.

@cleterodriguez ??? There is no v10. pfSense 2.5.0 was just released a week ago.

@valnar Be sure to read Recover config.xml From Existing Installation in the pfSense book. It makes reinstalling very easy. [image: 02_rescue.png] You'll lose your RRD graph data so be sure to back that up first if you want to restore it later.

That is a dns failure. Does it have a valid WAN? Can it ping netgate.com? If you have a backup config just re-install from USB. Open a ticket to get the image and instructions: https://go.netgate.com/ Steve

@vmb Looks like they already thought of that with the installer. It has the option to recover the config.xml file. Recovered the file then just reinstalled. All working (mostly). Thanks.

Can someone help me please. I have the same problem. Please wait while the update system initializes i am now on 2.4.5-RELEASE-p1 Do i need to update to 2.5.0 ??

@breusshe I ended up finding a setting that was different between my old vpn setup and the vpn company setup for 2.5. I changed that and everything suddenly worked. I still can't really explain why though. The entire time my VPN would connect but it did not appear to route traffic. No log entries that I could find that told me what was happening on that end either.

@svengru said in Clean install of 21.02 on ZFS filesystem not booting: I am running ZFS in UEFI. To answer @johnpoz question: Do a normal install using the USB stick and select ZFS. At the end of the process, it will ask if you want to make changes to the system installed. The fault answer is "NO". Select "YES" and you will get to the shell. In the sell you can edit /boot/default.conf using vi and add the line to it. If vi is not a tool you like than the following should do the same: echo 'zfs_load="YES"' >> /boot/loader.conf I confirm that running this command in the shell at the end of the installation worked well for me, and enabled me to perform a clean install of 21.02-p1 with ZFS on my SG-5100. echo 'zfs_load="YES"' >> /boot/loader.conf

No it's not easy as it requires downgrading FreeBSD. re: IPv6 see https://forum.netgate.com/topic/160952/ipv6-no-gateway-after-2-5-upgrade/17 for a possible workaround.

@steelcitycolt said in Can’t Boot after 2.5 Upgrade: correctly I'm assuming you've tried it a couple times by now. No idea what hardware you're running, but you might want to take a peek in the BIOS to see if there is anything ... frisky ... that needs to be disabled. I know I've had to disable a few oddball and unnecessary CPU power save features, any kind of 'auto' support that is supposed to help windows load on a machine, etc.

@lt1360hp You may need to inch forward on your restore using the selective restore options on the "Backup & Restore" page. Take what you need, leave the rest. Then install packages manually from the new install. [image: 1614451274840-0623ae4d-b71c-4e46-98d1-15159396a511-image.png]

@fireodo yep, great job to all the developers. thanks

@gertjan In that case apply the Last Resort option. now i have to it crash And no longer works

@internetxs I had some issues with my 5100 and wireguard. Decided to just do a fresh install of 21.02 (I had updated my 2.4.5p1). Since doing so, I've had no issues.

I tried it again with a copy of the original VM. Still the same error. Seems to be an incompatibility issue with Proxmox or their Bios.

Thank you for all the input. "Network is unreachable" got me thinking of the GW settings. The FW have dual WAN with policy-based routing and the default GW was set to "Automatic". After I manually selected a WAN interface as the default gateway, the FW managed to get information about the new 2.5 version. Thanks for all the input and help!

You couldn't have, one of a couple things must have happened: The USB stick didn't actually get written with 2.5.0 for one reason or another Your disk, if it's an SSD or similar media, has failed into a read-only mode and the writes from the installation didn't actually happen on the disk, so it's still running the previous version. The second reason could also explain why the upgrade failed. There are other potential causes but they all center around the hardware in the unit, not the installation image itself.