@fuckmakingaccounttoseelink Guide for restoring config from USB: https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-using-the-external-configuration-locator-ecl

The LAN settings for the installer are used by the installer, but it's not fully implemented yet, and optional. For example, there could be a web-based installer, or you can SSH in and perform some pre-install configuration if needed.

As for the WAN/LAN settings being exported to the fresh install, that's in progress and will be in the next installer release, it's already being tested internally.

I too have this exact problem.

Just set no gateway or set the WAN to DHCP at the initial assignment. Then access it via the WAN and enable the non-local gateway option.

If you really have to you could probably set that at the command line but I'd have to go through and check.

The servers should still be accessible.

But I would just reinstall 2.7.2 and restore your config.

@Gertjan it didnt but I did try it earlier on.

It was weird the only thing I have changed in months was adding DHCPv6 which is why I set it back to none. I guess it could have just been unrelated and fixed when it rebooted but I thought i should mention it as thats what I did.

@SteveITS

that answered it. many thanks!

@t44hunt92 the new installer support VGA

https://docs.netgate.com/pfsense/en/latest/install/download-installer-image.html

This installer works with both serial and VGA consoles.

@santammapr said in Unable to install pfsense 2.7.2 (no internet connection, no proxy settings):

Is this an offline installer: pfSense-CE-2.7.2-RELEASE-amd64.iso.gz

Yep, that is an offline installer.

@patient0
Hi,

I am facing the pfsense Crash report . Its fressh setup. The firewall keeps rebooting.

db:0:kdb.enter.default> bt
Tracing pid 0 tid 100283 td 0xfffffe00dc1841e0
kdb_enter() at kdb_enter+0x32/frame 0xfffffe00dc68aa10
vpanic() at vpanic+0x163/frame 0xfffffe00dc68ab40
panic() at panic+0x43/frame 0xfffffe00dc68aba0
trap_fatal() at trap_fatal+0x40c/frame 0xfffffe00dc68ac00
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00dc68ac60
calltrap() at calltrap+0x8/frame 0xfffffe00dc68ac60
--- trap 0xc, rip = 0xffffffff80e24c30, rsp = 0xfffffe00dc68ad30, rbp = 0xfffffe00dc68ad80 ---
ether_input() at ether_input+0x50/frame 0xfffffe00dc68ad80
re_rxeof() at re_rxeof+0x2c0/frame 0xfffffe00dc68ae00
re_int_task() at re_int_task+0xcf/frame 0xfffffe00dc68ae40
taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe00dc68aec0
taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe00dc68aef0
fork_exit() at fork_exit+0x7f/frame 0xfffffe00dc68af30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00dc68af30
--- trap 0x242424, rip = 0x24242400242424, rsp = 0x24242400242424, rbp = 0x24242400242424 ---
db:0:kdb.enter.default> ps
pid ppid pgrp uid state wmesg wchan

@stephenw10
i upgrade it to 8GB
snort
squidGuard

@Gertjan I had no idea about the RSS feed for the dashboard... it was not there by default. Good to know! Thx.

@jimp you're my savior!!
Oh my... thank you thank you thank you!!!

@svandive

I foolishly also made this assumption thinking it should have just worked out of the box.

The issue im getting is after various permutations messing with CSM, secure boot, various USB sticks and other variables, i still cannot pass (this is just past the splash page to even install pfsense). The only thing left i havent tried is a BIOS update.

Loading kernel...
/boot/kernel/kernel text=0x1a4c98 text=0xff3048 text=0x17ed568 data=0x180+0xe80 data=0x24c808+0x3b37f8 0x8+0x1d4108+0x8+0x1e9a19-
Loading configured modules...
/boot/kernel/zfs.ko size 0x619a40 at 0x37be000
/boot/entropy size=0x1000
/boot/kernel/opensolaris.ko size 0x1e2a8 at 0x3dd9000
/etc/hostid size=0x25
staging 0x67e00000-0x6c51a000 (not copying) tramp 0x6c51a000 PT4 0x6c51b000
Start @ 0xffffffff803a5000 ...
\

Going forward this should be less of an issue. We reduced the memory requirement for pkg by using a different compression.

I mean it's definitely more secure to stop passing traffic until the admin corrects a config mismatch than to just keep passing traffic on what might be correct. For example this is the same situation you might hit after importing a config into entirely new hardware where no NIC/Interface can be guaranteed.

I agree though it would be better to tie the interfaces to a specific MAC to prevent re-ordering. But doing so is non-trivial.

There have been a few feature requests open for this over the years. Like: https://redmine.pfsense.org/issues/410