@PlasticTarot What do the logs say after the restore/reboot? It should install the packages. DNS working on pfSense itself?

I found the update check can take a while, try your attempt again in 5-15 minutes. I recently upgraded several from 24.03 to 24.11 and had to wait on all of them to start it. Didn’t seem to be an issue yesterday coming from 23.09…

@stephenw10 Tks my friend.... A project for this week end when my wife goes to sleep :-)

And my customers too.... ( I have 2 sites... Site two can handle the load ( eMails gateway..... oops I'm sharing too much)

Yes, that should be fine.

@stephenw10
That was the DNS resolver configuration issue.
Outgoing Network Interfaces was set to "ALL".
I have changed it to "Localhost"
Decided not to use DNS Query Forwarding in the resolver.
Enabled DNSSEC Support.
Enabled Prefetch Support and Prefetch DNS Key Support.

All packages restored successfully.
Now I understand why my upgrade 2.6.0 to 2.7.0 was painfully slow.

@parry

Normally, I don't enter "admin" neither my password, the browser (Firefox 135.0.1) handles all that ^^
But, when I was entering a random password, after 2 retires, I was locked out.

I totally forgot that I whitelisted my LAN IPs (LAN and OpenVPN access) ..... but only IPv4.
Or, IPv4 is rarely used on my LANs these days. Its all IPv6 now.
So I got myself also locked out, like you.
There is no 'you are locked out' message on the screen, because the browser just can't connect to the pfSense LAN IP anymore ... no more replies .... it was hitting a wall, no like talking into a black hole.

I 'corrected' the issue :

c41b739a-eee6-4195-a819-b83d4997e9d5-image.png

2a01:dead:beef:a600::/56 are all 256 of my ISP IPv6 prefixes. This will do for the moment, although with that setting I totally disabled all login protection ....

edit : btw : not really a pfSense thing. Every network device with some security in mind does the same thing. Not the stuff you buy at Wallmart, of course.
Try entering 10 times the wrong ID code of your iPhone after power on. You'll see what happens .... (read about this before trying or you will have huge regrets !!)

@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. 😉

@stephenw10 thanks! I’ve sent it on the chat

@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 .

It definitely uses com1:

uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 16 flags 0x10 on acpi0 ... uart0: console (115200,n,8,1)

Same here. Thank you @jimp

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