No problem, glad I could clarify. 👍

If if gets fixed it will be in 25.07.

@SteveITS I agree, I thought that may have been an issue so I restarted the VM setup ensuring the disk was fixed at, I think I set 15GB? Still ran into the same original issue where it wouldn't format initially. 🤷

@Gertjan and others:
It was very helpful to understand that pfsense has a lockout which I had not seen before. What complicated issues further was that every now and again the connection between my browser and the pfsense firewall would go down momentarily. I traced that to an Ethernet NIC - after testing it with other machines. I would just watch the ping between 2 workstations connected directly by ethernet with no intervening switches or routers and every 2-20 minutes, the ping would not be returned for maybe 20 seconds. I am sure that this did not help. Exactly what effect it would have, I'm not sure - maybe receiving a spurious version of my pw etc. But I admit that I don't really know. So perhaps this was a combination of being locked out, problems with the NIC and general incompetence on my part ;)

As far as I can tell, there are no remaining login problems. So thanks to all who responded.

Check Diag > System Activity. It might be a stuck pkg process.

Yes, that should be fine.

@stephenw10

@stephenw10 said in SG-1100 Won’t Reboot on Upgrade - no internet access!:

Yeah I could see that. Thanks for the feedback, I'll pass that up the chain.

Much appreciated!

My new 1100 came in and is hooked up - no problem with that! I still have the troublesome one here, with pf+ on the USB stick. If there's anything I've encountered that it would help if I tested it, this is a good time to do that. I don't think there was anything outstanding, just the issue of pass-through and the subnet range. All the other issues that are unresolved could be explained if the internal storage is wonky.

No worries. It is a legitimate bug. You should just be able to import it. But because it's already fixed it's unlikely to see much traction in 2.7.2. At least there's a relatively easy workaround. 😉

@mircea-manea The NDI changes if you change NICs. If you contact Netgate I believe they will move the license, possibly a limited number of times.

Or remove the NIC...

Hmm, so what changed? Were you using the non-serial memstick previously?

It depends what OVH wants.

1:1 NAT is useful if one that one host will ever use the IP address. Just remember there are no firewall rules added automatically. You need to add rules for everything required.

@stephenw10

thanks for your support.

I install it from scratch and import the config and it is working fine know.
I don't know what was wrong.

my advice to everyone is that to make daily or weekly backup at least if you don't change the config a lot to save your life .

That's how Hyper-V works. You need 2 External switches.

If we summarize the three modes of Hyper-V switches are capable for:

External switch: It links to a physical card of the Hyper-V host and enables network access.

Internal switch: The switch isolates the VM but enables network switching between the Hyper-V host and the VMs.

Private Switch: It completely isolates the network from VMs.

EDIT - Don't confuse Internal/External with LAN/WAN.

Yesterday, I installed the stable version of pfSense on the stable version of VirtualBox without any problems. Apparently, a bug has been fixed

You might be running into this? https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-shrink.html

Yes, thank you and Stephen, I see I can recover almost 6GB of space.

@hockeyfreak said in Really confused about upgrade:

I would be tarred and feathered

Ha best avoid that then! And yes reinstalling is the better option here if you can. 👍

@stephenw10
Fun is more positive than my reaction!

@HansWerner3dit said in No packages in available packages list:

I am not skilled enough to restore the current setup from scratch [Wireguard, WAN Backup, Gateways, VLAN, DHCP6

You are ^^ and it's easy to understand why.

Always keep a recent copy of the pfSense config : Diagnostics > Backup & Restore When you re create or re install pfSense on the same device (same hardware, or to be more precise : same network interface NICs) then all you have to do is : import the pfSense config (same place Diagnostics > Backup & Restore), and your setup is done.

Example, one or two versions ago, the filesystem changed. This means the partitions on the drive being used have to be altered. A simple GUI or console 'upgrade' can't do this.
You need to get the firmware on an USB drive and see pfSense Documentation, look for the word 'Etcher'. Also find the doc about installing pfSense with 'ZFS'.
When pfSense starts, do a minimal WAN/LAN manual config.
Ones in the GUI, import your backed up config.
Done.

Updated four to 24.11 yesterday and all four ran into this. All I had to do was wait 3-10 minutes [depending on device speed?] until the message disappeared upon refreshing the page. I noticed the log shows the time gap:

Feb 4 19:49:24 pkg-static 47515 pkg upgraded: 1.20.9_1 -> 1.21.3_4 Feb 4 19:42:38 check_reload_status 759 Syncing firewall Feb 4 19:42:38 php-fpm 5569 /pkg_mgr_install.php: Configuration Change: admin@10.x.x.x (Local Database): Saved firmware branch setting.

The upgrades seemed normal after that.

@stephenw10 Thanks again, I so appreciate you taking the time!

And I'll comb through the XML file next.