Yup, that should be good. The config should always be importable into a newer pfSense version. Though I would not recommend using a config from 1.2.3 maybe. Steve

Yes, be sure to set the total log size limit in Snort as well as the individual log limits to prevent duplicate files filling the drive.

İf anyone will help me i'll be appreciate. Thanks and Best Regards.

@onlyfor1question said in pfSense installation hangs at a certain screen: @NollipfSense I just tried using that and I got the same error. Sounds as if you're having hardware issue...try pfSense 2.4.5rc to see whether you have the same exact issue.

Perhaps the computer you're connecting from is still using 192.168.2 address and a /24 netmask. If so change its address to 192.168.10.something and see if you can connect. Then make sure you have the DHCP server set to give out 192.168.10 addresses.

I think you need a radius server to put you in a vlan. You can use freeradius with pfsense.

Hello! This might be an option if you can grab the current config.xml : https://docs.netgate.com/pfsense/en/latest/backup/automatically-restore-during-install.html John

I did a clean install from an iso and restored the config and all is well! Thanks!

@n1l0c said in No LAN internet connection on initial setup: The problem is I can not reach the internet from my LAN network. What exactly does that mean? What error message is returned by your browser when you try to access a site? Can you ping 8.8.8.8 from a LAN client? Can you ping www.google.com from the same? Can you ping 8.8.8.8 from the firewall in Diagnostics > Ping? Can you ping www.google.com from the firewall in Diagnostics > Ping? Can you resolve www.google.com from the firewall in Diagnostics > DNS Lookup?

Thanks everyone for the recommendations. I do know what I plan on getting now. Thanks a bunch everyone.

@Gertjan Thank you VERY much! I appreciate your time and effort!

It's an assumption based on having seen similar things when investigating the UEFI/legacy install issue previously. The 2.4 installer is pretty much the FreeBSD installer but 2.3 used our old installer which was quite different. I suspect in 2.4 it was booting the USB UEFI and installing UEFI and then not booting that from the disk. 2.3 did not support uefi so it would have installed legacy. the upgrade would not have changed that. That machine does not seem that old. I imagine it probably could have booted either from HD given the right bios setting. Steve

@kiokoman Thank you for your reply. It's now working.

Something to think of when you update or upgrade : After the backup of the config, and before the upgrade, reboot. Wait for it to 'settle' down en check basic network activity and recent log line entries.

Yup that is BORKED ;) That is the official technical term btw ;)

The ntp status of the fresh pfsense 2.2.4-p3 as opposed to the screenshot above which is from a pfsense 2.4.4-p2 to pfsense 2.4.4-p3 upgrade. That system had run for about 2-3 years with only one time sync issue before the upgrade. The ntp service was disabled before the upgrade. [image: 1583002226640-newinstall-hdd-ntp-screenshot.png] I am STILL trying to determine whether this is a faulty RTC timer on the motherboard or not. Dell BIOS diagnosis says everything is good and the system seems to be holding it's BIOS time with the new battery installed. I am going to run this fresh install/new SSD for a week or so and see if it also gets the time sync issue - if I understand it correctly it may not show itself for a few days to a week?