OPNsense Forum
English Forums => 24.1 Legacy Series => Topic started by: chrcoluk on February 26, 2024, 08:13:16 pm
-
Is there a way to just boot into the installer without it attempting a live boot?
It pauses on WAN for about 15 minutes, and then stops on starting ntp service. These problems are likely that because I am booting in a test environment where is no working WAN connection.
I have tried giving it 2 hours, and its still sitting on starting ntp service.
-
Unplug the WAN cable and it should be OK, had the same thing happen to me today. You can plug the WAN cable back in after the installer finishes.
Alternate would be to image the NANO version to the hard drive and let it do it's thing. It may still get stuck on the WAN and NTP connection so this may or may not fix the issue.
-
Thanks, that does work.
-
Strange. What sort of WAN are we talking about here?
Cheers,
Franco
-
In my case, it was a LAN address and they have the ports set to auto-trunking, it takes like 45 seconds to get a DHCP address. On each reboot the system sits at configuring WAN for a long time while this happens.
And since we aren't using a network based installer, the only issue might be if we are reinstalling on a unit that is in place. Otherwise I tend to set mine up with no connections anyway, get most of it configured, then start making connections. A minor thing to me so not really worth reporting, especially when it is probably an issue on my end.
-
If you have trouble with WAN in those cases you can also avoid the auto-assign and just manually assign a single LAN interface when prompting for assignment and set up the rest later.
Cheers,
Franco
-
Strange. What sort of WAN are we talking about here?
Cheers,
Franco
In my case its not even WAN as the auto assignment wrongly assigns the port.
OPNsense running in VM, two nic's one for WAN and one for LAN, it assigns the LAN port as WAN, and vice versa and I have to wait quite a while on the live system boot, interestingly the first boot post install is much quicker.
-
It's not "wrong" in any sense of the word. It was always done this way. Other firewalls changed it after we forked.
There is no right or wrong, just preference (and the ability to set your adapters or cables in a matching policy). And while the automatic defaults are good to have manual assignment is ussally good if you don't want the defaults.
Cheers,
Franco
-
I am just giving you an answer which might explain why it sits there for a long time on the installer boot. I could I guess revert the assignments on the host and see if it speeds things up.