Send me your NDI in chat and I'll check it. It would almost certainly have been the NIC change that caused it. Steve

Yes that's the correct installer file.

"pfSense Plus Public Cloud Firewall/VPN/Router"

Yup I can remove it if you send me your NDI in chat. But you should be able to enable the CE branches and install that in the installer. Or use the legacy CE installer. Steve

You can go straight to 23.01 but I would backup the config and reinstall clean from a version that old. It will ultimately be quicker and cleaner. https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/reinstall-pfsense.html Steve

Hmm, the logs seem to show that it's the dhcpleases process. However that does not (yet) work with Kea. And it should not shutdown the DHCP server, it restarts the DNS server. However I would try disabling resolving dhcp leases in Unbound if it's still enabled. It should be disabled automatically when Kea is enabled.

@stephenw10 well yes that. Plus ultimately the upgrade from 23.09 to 24.xx killed the OS which bricked the device.

That's a library mismatch. At some point it has pulled in packages from a different version. If that happened at upgrade it's probably not an issue unless it reappears after clearing it. Those errors always show at upgrade but are usually suppressed and would not create a report. Steve

I had the same problem. For me, it was a faulty console cable that caused the exactly same issue. With a different console cable, the problem did not occur.

@MLBiedler prob because the built in one in windows doesn't actually understand that common compression method used all over the planet..

it's sorted now, opened a support ticket and netgate reassigned the token to my new NDI.

@stephenw10 ok cool. thanks for your assistance on this.

@viragomann Thank you very much for your support.

It waits for 3 seconds and shows a countdown: TIM-1.0 WTMI-devel-1.0.0-1115f12 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.237V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL1: Built : 14:34:11, Feb 7 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL2: Built : 14:34:13, Feb 7 2020 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL31: Built : 14 U-Boot 2018.03-devel-1.2.0ROGUE2-01.00.00.02+ (Feb 07 2020 - 14:33:22 -0500) Model: Silicom Rogue-2 CPU 1200 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 750 [MHz] DRAM: 3.4 GiB Comphy chip #0: Comphy-0: SGMII1 3.125 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps PCIE-0: Link down MMC: sdhci@d8000: 0 Loading Environment from SPI Flash... mvebu_spi_ofdata_to_platdata: ofdata clock 200000000, frequency 20000000 SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Silicom Rogue-2 Net: eth0: neta@30000, eth1: neta@40000 [PRIME] Hit any key to stop autoboot: 0 Marvell>> Pressing space (or any key) should stop the boot. If it doesn't then perhaps your terminal setup is not sending it correctly. Steve

After a lot of struggle this was my solution; It seems a static ip in the 192.168.1.x range is restricted so I changed the ip address of my isp router to 192.168.13.x. Powered off my pfsense1100 booted with usb (only the righter slot works) and pressed the [y] button a couple of times to prevent autoboot. Then I started the ‘recovery’ instead of ‘install’. And in the recovery I only opened the shell to ping a website and confirmed that my internetconnection was working. Then I typed exit to start with the install. And everything worked instantly. During the install you get at 3 moments the feeling that everything is stuck. Especially during the last stage, -the real install- just wait for like 10 minutes.

Everything is running now. The DNS problems resulting from a misconfigured gateway. Thank's for your help. Johannes

Now I did the following: env ASSUME_ALWAYS_YES=yes pkg-static bootstrap -f After that I went to System Update and it showed that I have a new Version available. Before that it always showed that 2.7.0 is the latest version for PfSense. So I updated from 2.7.0 to the new stable version 2.7.2 After it upgraded and rebooted (it felt like it took much longer than usual) But now it seems to work somehow. The package manager shows items and the crash report does not show up anymore. I think the issue is no more. (I hope)

@stephenw10 No, 2.5.2. I am afraid I am a little behind... not proud of it though...

Ah, then, yes, 2.7.0 is the last version that will see packages there. The dynamic repos will not pass branches to CE in Azure.