Hello, Please open a ticket at https://go.netgate.com, Please provide the serail number of the unit that is not working, we will be able to take a look see what we can do to help you out.

In reference to: You think they'd have tested this on Netgate hardware.
We do, extensively, it sounds like there might have been a physical issue causing this problem (bad RAM, storage or other board level component died).

Thanks Steve for your confirmation that no security updates will be released for x86 hardware. I'm already looking for some 64-bit hardware to install PfSense on.

No and No. But if you only need 8 ports that's pretty much what the XG-7100 is. 😉

Steve

No, nothing has changed there. There is no MIPS support.

Steve

@esm said in issue to update the rules in snort:

The package with this version version 3.2.9.8_4. is snort or pfsense?

It is the Snort package. Go to SYSTEM > PACKAGE MANAGER and you should see a Snort package update posted (unless you are already running the latest version). It might also help you troubleshoot your problem if you will look at the Update Log that is accessible at the bottom of the UPDATES tab page in the GUI. You will see a button down at the bottom of the page to view the update log. Look in there and see what error is being returned by the failing update.

Yes, i ssh'd into the box and after "Status->Filter Reload" or any other action , for example changing a
Rule make the terminal unresponsive and after 1 Minute i got the message "Session closed".

BUT
i have done some additional tests right now , and it's working at time 🤔 🤔 🤔
Don't know whtas going on.
i will watch the situation for a few days ....

Many thanks for your help Steve

and to answer the rest of your question: no advanced state killing options selected

@grimson said in upgrade from 2.4.3 to 2.4.4 failed. no wan and no webui:

@f3dr
https://forum.netgate.com/topic/135395/where-to-download-old-versions/5
I've read that post and probably missed that bit, sorry.

https://forum.netgate.com/topic/137600/how-to-install-pfblockerng-if-you-don-t-want-to-upgrade-to-pfsense-v2-4-4/2
Totally missed that as I was just focused on fixing the broken firmware first. Thank you anyway!

Next time don't be lazy and search yourself.
I think I've not been lazy, just searched in the wrong places. I will try to improve my research next time and I will check all the possible problems before attempting the update! Thanks

Thanks for your help @grimson

As with all the others asking similar questions, do a fresh install of 2.4.4 and restore your config. Packages will not work on outdated pfSense installations.

Also learn how to search the forums an do some RTFM.

Ignore i was using the WAN IP address to create the rule, when i should of been using the public facing local IP

which in my instance was 172.16.1.116

@radenthefridge

Got it. Ive never had to do a VLAN past the modem on any incarnation of DSL Ive used from Centurylink. Includes the MLPPP setup we had with a 3rd party ISP up to the last bonded connection using the actiontec C2000 in bridge mode.

I followed this guide from Centurylink https://www.centurylink.com/home/help/internet/modems-and-routers/technicolor-c2000t/advanced-setup/wan-settings.html and then set up my pppoe credentials on my wan interface.

Before this modem I was using two Zoom 5715 (bridge only) modems.

Good Luck!

I assume you mean a load-balancer in AWS itself rather than another VM running there?

The routing there could get ugly!

Steve

Not enabling DHCP did it. Not sure why that would even be, but it worked, many thanks

Hi, I've faced the same issue, just now.
I run couple psSense 2.4.4-RELEASE as a virtual machine on a XenServer 7.2.0 HA cluster without any issues about 2 years.
Before now, I used dedicated virtual network interfaces to connect virtualized pfSense VMs to my VLANs. Couple days ago I decided that its time to connect pfSence to a trunk and configure VLANs on it.

I did it and it works but with MTU issues. It looks like it works but at the same time, heavy traffic like SMTP over TLS doesn't go through or heavy https web pages can't be opened. 1469 is the largest ICPM packet size can go through the VLAN interface.

So, I would appreciate if anyone can help to resolve the issue and a specially if the topic starter can share his experience and explain what was wrong with the kernel drivers for the server NICs.

I did the upgrade, just by backup the config and restore the config on 2.4.4 - with no problems at all.

One interresting thing is that the upgrade I now got almost full speed in down/upload.
With 32 bit 2.3.2 : 200/300 Mbps
With 64 bit 2.4.4 : 700/950 Mbps
My line is 1000/1000

We are working on it! But things get significantly more complex if the existing config already has vlans or laggs for example.
Then there's the switch config, you might set it as 8 separate ports but some users don't want that. There are many combinations. A compromise will be reached.

Steve

Ok so it appears to have been an issue with our Zyxel GS1500 PoE switch. I took my phone home with me and tested it from there. It worked perfectly. Brought it back to the office this morning and it just started working. Maybe it just wanted a change of scenery or something ;-) but anyhow it's working now. My colleagues phone on the desk next to me (we're all plugged into the same PoE switch) still wouldn't play ball however. So I unplugged it, walked over to another desk and plugged it back in. Low and behold it starts working. Unplugged it and went back to his desk and plugged back in - doesn't work. Walked over to the PoE switch and moved his connection to a different port on the same switch which got him up and running. Repeated procedure for other phones (All Yealink T46G's) and now all is back to normal.
So something in that managed switch (which we don't actually manage, it was left as was out-of-the box) was interfering with traffic somehow. Incidentally there are no PC's on that PoE switch only phones, that aspect sadly didn't occur to me until now otherwise I might have rebooted it for the sake of it. So thanks for help guys but it turned out to be something basic in the end.

There was a memory leak fixed in Unbound that I guess might have exhibited this. Maybe if it started swapping and got progressively worse. That should have been fairly evident though either on the pfSense dash or the VM performance graphs.

Steve

Yes, 2.3.X is End of Life. There will be no further security updates for it.
https://www.netgate.com/blog/pfsense-release-2-3-x-eol-reminder.html

Steve

@jimp Perfect, thank you for the details. My patch is set up to not auto re-apply after upgrading. So I am set this time. (In the past, I once reinstalled pfsense for good measures after forgetting to revert a patch because I was not sure about these details.)