@stephenw10 Thanks I was able to get it installed to the flash drive.

wan was getting the ip, can ping but from console but not allowing connection from devices - ended up resolving the issue as needed system backup urgently so installed another product, which worked straight away

Ah.......it wasn't DNS this time, but it was IPSEC. It was some pesky IPSEC that wasn't fully enabled, only enabled on one side. A few months ago I was going to setup some IPSEC stuff but gave up on it' I guess I never disabled it. I went ahead and disabled my half-assed IPSEC and now it's working. I want to thank everyone for their help. Appreciate it. This was a tough one for me.

On the older version those fields were not properly protected, so if someone entered a character that was not valid xml (such as an accented character) it would cause the config to be tossed out. Those characters are fine to have inside CDATA tags, though. We don't go too nuts with the CDATA encapsulation though because it adds a bit of extra data to the config, making it larger.

The issue has been resolved. The issue was a result of a bug (#9144). Just in case someone else is running into the same issue, the solution is: Assign a static IP to your PC, then enter the web interface at the IP address set in the previous step, and enable DHCP from there to prevent crashing. Link to bug report: https://redmine.pfsense.org/issues/9144

If you were hitting that DHCP issue you would not see a change in the routing table only the interface MTU. The ARP resolve errors imply the gateway is not responding to ARP. Try running a packet capture on WAN to be sure it is actually sending the ARP requests and that the gateway is really not responding. Steve

@stephenw10 said in Upgrading from 2.3.4 to 2.4.4 on pcEngines APU2: @brianlloyd said in Upgrading from 2.3.4 to 2.4.4 on pcEngines APU2: I would put in an mSATA drive but I don't think it will fit in the enclosure provided by pcEngines for the APU and APU2 boards. I would be amazed if it doesn't. mSATA is a slot on the board, there is almost no way they could make an enclosure that didn't fit it. We fitted mSATA to APU1 as an option and I believe the APU2 shares the same footprint. Steve Oh. Looking at the board I see one of the slots I thought was PCIe is labeled mSATA. Yes, that should work. I have an mSATA board on the way. I'll move the system onto that instead of the SD card. Thanks!

That doc only applies to the XG-7100. In most C3000 systems all 4 ix NICs from the SoC would be brought out as ports directly. Steve

I have done this using this guide, Its very accurate.. http://timita.org/wordpress/2011/07/29/protect-your-windows-laptop-with-pfsense-and-virtualbox-part-1-preamble/ Hope it helps you ...

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!