I think it could be memory issue, it just fails with power saving modes  and it can be stable under load, when full voltage applied. To check this you need to install memtester package. For 2.4  version it would be: fetch http://pkg.freebsd.org/freebsd:11:x86:64/latest/All/memtester-4.3.0.txz pkg install memtester-4.3.0.txz to run, use memtester (size to test in MB) (loops) memtester 512 10 Memtester for other FreeBSD version can be found here — http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=memtest For examle 2.3 pfSense based on freebsd 10 needs this package http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/memtester-4.3.0.txz If pfSense also would not hang, then it definitely memory powersavings incompatibility issue.

Seems most people in this thread is refering to the monitoring rather than the traffic graph. My traffic graph is working, but the monitoring section is dead. All metrics show as 0 On snmp it reports 0 on all but memory (mempool).

Hmmm, yeh. It looks like the next time anything does "check for updates" that it overwrites here. Anyone got a better idea?

AWS 1:1 NATs the elastic IP to your interface address.

! interface FastEthernet0/35 switchport access vlan 105 switchport trunk encapsulation dot1q end As has been said, get rid of the trunk config on your edge device (access, untagged) ports. There is zero reason for that to be there.

I use Notepad++.  Thanks guys.

@pmass: even if one pray while rebooting ?  :) Perhaps if you pray for butterflies… :)

Just since this comes up fairly high in the relevant searches on this subject, and never got a resolution: cmb is correct in that you have only to change the track and run the update. When you check for updates it will still show an experimental release number as an available update. Run this update and then reboot. Once it comes back, it will show an update available that will be the release version. This was my experience going from a 2.3.3 pre-release anyway.

well that was simple it worked Thanks

I don't know what the issue was…but I backed up my config.xml, rolled back my VM to a snapshot from a few weeks ago, restored the config.xml, and am able to run the update(s) now.

Well, the only "solution" is to kill as many services as possible (and that includes ntpd, nginx etc.)

Thank you DotDash!!

That is not a similar problem at all. Please start a new thread for that.

"failed horribly" how? We tested 2.3.3 on ALIX (I've been running it on my ALIX for months), and we tested upgrading from older versions in various stages (e.g. 2.2.x to 2.3.3, 2.3.2-p1 to 2.3.3). There isn't a way to get back to just 2.3.2-p1 at this stage, since it was an errata release. Fixing your setup to work with 2.3.3 would be simpler.

Exactly what Asus device are you referring to here? Everything I can see that might be an 'AC-1300' is already a router and not pfSense compatible. Steve