@goodthings said in fatal error - cannot restore 2.4.2 backup in 2.4.4: Unfortunately I don't have portal access. In an act of pure desperation I searched github for the function "function upgrade_174_to_175()" and found that it relates to ipsec phase1. The (non-functional) 2.4.2 config looked like this: <ipsec> <phase1></phase1> <logging> [...] </logging> </ipsec> I compared it to other configs and manually deleted the empty "phase 1" element. The configuration upgraded successfully. <ipsec> <logging> [...] </logging> </ipsec> That was a bit of a nightmare. Thanks for this bit of information. I was reinstalling from a rather old configuration file and my XML file just had a <phase1 /> line. After removing that the configuration installed properly. Without removing that my dashboard was extremely slow to load and my NIC assignments would not persist on reboot.

@edz it's not :) It's a VMware Fusion virtual machine. Much easier to do testing on VMs where you can do snapshots, and have better performance.

Sorry for late reply. I got it fixed by installing on an HDD and putting that HDD into the System. Then booting it and it worked.

Upgraded to 1343 with pfblocker-ng installed, no problem here.

Usually when you see this it's because you are resolving the IP from an FQDN not refined on the firewall, so maybe a dyndns client running on something else or just a static DNS entry. You can disable that check in Sys > Adv > Admin Access if you know it's correct. Or you can add the hostname you are using to the list there so it accepts it. Steve

@kimzer said in Fresh pfSense 2.4.4 install. Console spam and random internet loss: Also, the console is spamming: "fwohci0: device physically ejected?" "fwohci0: device physically ejected?" << its a firewire device https://forum.netgate.com/topic/19587/livecd-boot-issue-fwohci0-phy-int-repeating/10

Seems a workaround is to boot from the USB drive, but first changing the boot options firmware from BIOS to EFI does the trick. This does not help with the CD ROM though, the only reason why I need to change from BIOS to EFI when using a USB boot is so the system will recognize the drive. Installation works fine now. We will see.

Yep, I second @rtoledo2002 advice as another non network expert. Keep it simple. Turn off wireless on your ISP gateway. I have a cable modem from my ISP with wireless and do the same thing. Buy a wireless access point. Many wireless routers can be put into AP mode as well. Plug the wireless AP into the Pf sense Lan. In my case, I plug it straight into the lan side switch of my sg-3100. Everything works nice.

I mean re-install the firmware so you know you have a good OS/filesystem. Then restore your config into that. Steve

@gwaitsi I disabled squid, and the swap goes back to zero.

@shiv_znet Please suggest for the same and let us know why we are facing such types of issue.

What is the error you receive when trying to connect? The default LAN address is 192.168.1.1, unless you changed it already.

There is not enough information in that header to tell what happened. You'd need to attach the whole crash dump file

Yes, you need to reinstall to get the UEFI boot slice and GPT loader scheme. Steve

This I assume?: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236716 That looks like bits vs bytes error to me. Are those screenshots still what you see? The links above have expired. Probably need an update to 3.8 though as suggested there. Steve