Nope.. I don't discount that there is an error.. But since we are not affected there is no way for me to know anything is wrong.. Do you see your issue reported here anywhere? https://redmine.pfsense.org/projects/pfsense/roadmap

Seems this is related to Unbound noted in this post

On Friday night 11/30 around 10-11 pm US Central time, checking for updates was slow and downloading the updates took a long time and failed frequently. I was able to restart it, but eventually walked away, and found a couple hours later that the check for updates and the downloads were normal speed. So I think it was on Netgate's end?

There is actually a separate setting to disable the http referrer check or you can add the external IP/hostname as you say. Or infact you can just disable referer sending in your browser just to get access. But what you should do is use the provided appliance in the marketplace. Steve

When importing/restoring the config file it should ask you to set up the new interfaces. Or you can edit the XML file before restoring. The restore will install any packages it needs.

@gil said in 2.4.4p1 Routing Error: I then reloaded the pre-saved config file This doesn't really help this time, but next time it might be informational to save the non-working config file first, and compare it to the saved one.

There is no factory default button on the XG-1537. It is a hardware reset button. To factory default you can use Diagnostics > Factory Defaults in the web gui, boot to the console menu and use menu option 4, or boot from a USB installer and completely reinstall from that.

I installed 2.4.4p1 without a hitch. There were some errors, but every thing seemed to come up. The cli command for the barnyard2 was not necessary for me :)

@chpalmer Perfect!! So simple! Thanks for the help. This forum is really an nice asset to have available. Thanks again!

Best practice is to use a subdomain of your TLD. So if you own domain.com, then use home.domain.com or lan.domain.com. It saves you from having to maintain split DNS.

Even better : access the console ! If memory serves me well, a Link Up (and down) event is signaled as soon as you hook up a cable - and unhook. It will mention which interface it is.

The crash report shows a file system error that would be independent of the loaded config. You can probably recover that by booting into single user mode and running fsck -y / a few times or you could just re-install 2.4.4p1 clean again. Usually that happens because of some power interruption during a filesystem write. Steve

Yes. And also into 2.4.4p1. (or any newer version) Steve

Ok, thanks!

You're welcome. Netgate special offer here btw: https://store.netgate.com/MBT-2220-system.aspx -Rico

You mean setting that still gives no serial console? And serial console is enabled in System > Advanced > Admin Access? That is the standard location for com2 but it might not be there on that hardware since they decided to use com2 as the console. Check the BIOS for any reference to the I/O location. Other than that I'm not sure what more we can do. You could try some other OS to see if that is able to use the console. Steve

p.s. Now, if pf also had a mechanism to install packages for previous versions we would all be extremely happy too. I strongly agree!

Thank you. I did not have to reinstall. The sg-2440 came up fine after a couple of reboots. For some reason it had just gone unresponsive and I figured there was some sort of corruption. Everything is fine now. Thanks Jerold

Two things I would check. First, make double sure your Oinkcode is typed correctly into the text box on the GLOBAL SETTINGS tab (I normally would not expect that to have been changed, though). Second, make sure your subscription has not expired (assuming you are using the paid rules). The Subscriber Rules subscription renews annually. One other thing to try is to manually attempt the update using the Update button on the page. I have seen instances reported by other users in the past where for whatever reason an update would randomly fail. Trying again manually at a different time would succeed. Lastly, make sure you have the most recent version of the Snort package. There were changes to the rules tarball naming convention that started with the 2.9.12 release of Snort. Those changes required changes to the GUI package code. The "Not Downloaded" message was a symptom of this. The latest Snort package works, though. Update to the latest Snort package if you have not already.