Yes, it will definitely have changed your NDI which is why you're seeing the repo check failures.

If you send me your NDI and order number in chat I can check it.

The i210/i219 NIC uses the igb driver and the x550 NIX uses ixgbe. So if you boot the firewall with a config that contains igb0-4 assigned it will drop to the interface assign screen at the console because two of those no longer exist That's expected.

Not really! If I could I'd try to replicate it that way but so far I've been unable to.

@Gertjan Thank you so much for the info.

Mmm, your WAN doesn't show an IP address at all. So if you're expecting it to pull a DHCP lease from somewhere then you probably have a L2 disconnect somewhere.

@P3R
Thanks for posting!

I noticed the firewall setting too. I think I've tried disabling it, not sure though.
Will test it again and report back.
Thank you!

Thank you @patient0, @stephenw10, @SteveITS for replying. The 2.7.2 update became available and the available packages are now listed after running "certctl rehash".

Yes you can still import an older config. If it's using some deprecated feature the config upgrade code will handle that.

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.