@unsichtbarre said in Please wait while the update system initializes: pfSense-repoc-static: invalid signature This was the solution: pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade pkg-static bootstrap -f pfSense-upgrade -d -c Found here: https://forum.netgate.com/topic/181308/version-2-5-2-upgrade-2-6-0-or-2-7-0/11

@_Adrian_ [image: 1694155654112-2ee19a44-6892-4003-b4f6-9ee36dfd21dc-image.png] You don't need the last four. If you're forwarding, double check DNS server 2 and 3, as these look like a black hole to me. 3 and 4 : ask what they do with your data. If doubt : ditch them all.

Send me your NDI in chat and I'll check it. Steve

Could be. There was an IPv6 issue at the servers a few days ago. I thought it had been fixed before you posted here but maybe not. It's fixed now. Steve

Hi @Gertjan I checked but unfortunately nothing works I tried the commands "boot /boot/kernel " , "boot /boot/kernel/kernel", "/boot/kernel " I can't read any file to check what could be the right boot command I m stuck at this boot prompt [image: 1693906050321-capture-d-%C3%A9cran-du-2023-09-05-11-27-14.png]

Scrap this - the following command worked for me: pkg-static upgrade -fy pkg

@MushyMiddle Did you follow the recommended practice of removing all installed packages and backing up your configuration before executing an upgrade?

@stephenw10 Thanks a million - fixed it!

@wgstarks Your issue doesn't exist anymore : you've updated to the latest version 23.05.1, so now pfSense knows where to look for updates for this version. If you see this here : [image: 1693557487536-6019a4c6-efd1-493f-b49a-5232a77c341c-image.png] you know you're good. You should see the 3 options : 23.09 23.01 23.05.1

@stephenw10 Yep, things are back to normal for me as well.

@SteveITS We are working with the AWS pfsense appliance, so we can be confident that the basic configuration will be stable (unless I add NICs or something like that). Our goal is to be able to deploy or restore the firewall without a human having to log in to load a backup file or look up a password or anything like that - just have the config.xml available and loaded automatically.

@ladae The above but by way of explanation, one has to upgrade to 23.01 before upgrading to a later version. The error message is protecting you from breaking pfSense; see my sig.

Yes, I have found that forcing a USB3 flash device to use USB2 often allows it to work. Additionally the opposite is often true. If a USB2 device isn't recognised try moving that to the USB3 port.

Not passing any traffic is not the usual symptom for a Realtek NIC that is detected. There is an alternative driver but to install it you would need to use some other NIC temporarily or somehow copy the pkg onto the box directly. Steve

@jimp Thanks for the response. Just sharing my experience with 2.8.0 ZFS and the offer to upgrade to 23.05.

@stephenw10 I tried it again to try to pull the logs. Instead of rebooting it actually stopped and complained about the base.txz not being valid. I re-downloaded and re-imaged and it worked fine.

The downsides of double NAT are: Much more complex to setup port forwards UPnP cannot work Traffic is still limited by the firewall and NAT capabilities of the other router. Sometimes that can be significantly limited for state table size etc. Yes setting the main router in bridge mode is the way to remove that. Leaving only pfSense NATing the connection. Steve

@tom-28 My issue was resolved by moving the SolarFlare NIC drivers from /conf/config.xml to /boot/loader.conf.local "sfxge_load="YES" Default file permissions are fine. Reboot, get a new activation token and everything worked.

Thank you!

@penguinpages said in Upgrade - Scheduled Window for upgrade: But many of my home devices show loss of communication (hense correlation to Router). And my laptop reverted to APIPA.. Which implies not just lack of router, but some kind of request or cyle that triggered IP release but nobody was around to renew. Sounds like your switching hardware or wireless went down.