Could this be related to
https://forum.netgate.com/topic/136595/lan-malfunctions-after-upgrade-2-4-3-2-4-4

Thanks

@grimson

Problem I am having with 2.4.4 is that my connection LAN and WAN wise has slowed down considerably, in addition I cannot seem to get ICAP Inteface for Squid and ClamAV integration to start up.

Maybe a backup of configuration and performing a fresh installation may resolve the issue...

@jimp

Sounds good. Thanks for the help!

In the config file this appears as tags:
<disablechecksumoffloading></disablechecksumoffloading>

Steve

Log in as root/admin or install the sudo package and use sudo from those other accounts (like linuxlover) to obtain root.

Other added accounts are not automatically root in the shell.

Yes actually I don't need 6GB RAM for this setup, but it is already there in server /Dell PowerEdge 840/. Next week I will make lab install of 2.4.4 on this hardware and will testing for some time. If everything looks good I will put it in production.

I split this into its own thread since it wasn't really related to the one where you posted it.

There are no known issues anything like what you report. It's possible that your upgrade did not complete properly, or there may be an issue in your pfBlockerNG setup causing it.

The first thing I would do is remove pfBlockerNG and then install pfBlockerNG-devel and force and update in there to see if the behavior corrects itself.

If not, then you'll need to provide a lot more information about your rules before and after the upgrade. Not just descriptions, but screenshots, /tmp/rules.debug, config.xml, etc.

You need to use the memstick image to create a USB stick to install from.

I suggest using Etcher to write the image to the stick.

Use this image if you are using a VGA console:
https://nyifiles.pfsense.org/mirror/downloads/pfSense-CE-memstick-2.4.4-RELEASE-amd64.img.gz

Steve

@grimson Actually I couldn't ssh or WebGui connect because I couldn't know it booted. I just saw it suck in booting. So you can call me dumb but I would like to know what would you do when finding a problem totally new to you. I tried what ever I could think for hours before coming to the forum but that wasn't something I could think because I don't have the experience. The link you sent I had already seen but it didn't help because it was VAGUE and for that reason unhelpful.Now, as for the marketed product names I am sorry if I can't read between the lines IN THE OFFICIAL PRODUCT PAGE and find that my intel called Celeron processor isn't a Celeron but an ATOM. So again call me dumb or an idiot and proceed.

Yup, it is/was: https://redmine.pfsense.org/issues/8910

Plus there are some other tickets covering related things.

It is fixed now and will be in 2.4.4p1 or is in current 2.4.5 snapshots if you're able to test.

Steve

It seems like the subnet between your ISP router and IPCop is 10.0.0.0/24. If you put the pfSense WAN into that subnet it's gateway must be ISP routers internal IP address. So I would expect to see the pfSense WAN set to something like 10.0.0.100/24 with a gateway of 10.0.0.1.

Steve

The only thing not backed up there would be packages pulled in directly from FreeBSD by specifying a different repo.
Those are not directly supported though
What did you actually have installed from FreeBSD?

Steve

Is it something that re-appears if you delete it?

If not it's likely an artifact from the php change during the upgrade.

Steve

@anh I am on Amd platform. Not sure if this help or not

A few more hours in, and the WAN is holding up, thankfully.

I'll probably release this feature in a snapshot in the next few days. The official -p1 release is harder to pin down since we never know what is going to turn up in testing - Likely weeks rather than months though.

@piba Good to know. That was my only concern.

Swapping in a straight up DSL modem resolved this issue. Looks like the draytek router was to blame, perhaps a power outage reset it into an unusable state etc.