@doktornotor: The way to fix this is to do a clean install and restore config.xml. The Snort widget sure like hell does not contain SquidGuard XML, your filesystem is toast. I got it to work! You gave me a clue that I had overlooked. Thanks! PHP is a foreign language to me since I don't do any web programming. Before I jumped into the frying pan and do a complete new install I tried something. Since the file seemed to be corrupt I deleted it (/usr/local/www/widgets/widgets/snort_alerts.widget.php).  I then tried the web interface again. The stuff in front of the dashboard was still there, but all of the menu items could be selected. I selected system –> package manager and deleted snort. It never came back and told me that it was deleted so I did a back space and checked to see if SNORT was still there and it was gone. The stuff in front of the dashboard disappeared and every thing seems to be to normal. All the function on the menu selections appears to be working correctly. I have not reinstalled snort yet, but it should work. I have not done a reboot. Could be a bad idea! What would have caused this? any idea?

I am connect to my home network through OpenVPN running on pfsense and can watch TV served from my HDHomerun Prime anywhere I go.

I just tried the same procedure here on a 2.3.3 firewall and there was no problem at all. Does that happen even before you press Apply Changes, or after? From the console, before putting that in place: cp /tmp/rules.debug /root/rules.debug.before Then re-create the issue and run: cp /tmp/rules.debug /root/rules.debug.after Then once you regain access, grab both files and compare the two using diff or similar, see what shows up. Like this: diff -u /root/rules.debug.before /root/rules.debug.after Normally you'd only see additional pass rules and they wouldn't affect anything on your local network.

"what is the default layer 2 routing protocol? " Layer 2 does not have a concept of routing as such.  VoIP does not really care how packets are routed either.  Perhaps you would be better off describing what your problem really is or what you are trying to achieve.  Either way, this is the wrong forum. Cheers Jon

After a clean install of 2.3.3 on my backup APU I made another attempt to upgrade the currently active unit from 2.3.2_1 to 2.3.3; this time I did it via the serial console, command "pfSense-upgrade". Not surprisingly, it worked perfectly this time  ;)

I also encountered this error, but in my case there was a circular link causing it: ls -alFh /root/var/cache/ total 4 drwxr-xr-x  2 root  wheel  512B Sep 28 20:10 ./ drwxr-xr-x  4 root  wheel  512B Apr 12  2016 ../ lrwxr-xr-x  1 root  wheel    24B Sep 14 14:21 pkg@ -> ../../root/var/cache/pkg (In case others stumble upon this thread.)

Indeedy clearing the browsing data does reset the graph. Than Johnpoz :)

It is interesting to read about all your views about Secure Boot and security concerns but If I understand it correctly freeBSD and therefore also pfSense have no support for Secure Boot yet so even if there are some benefits of using it the discussion is purely academic from a pfSense perspective. Does a strong BIOS password offer protection even against attacks with no physical access? Perhaps this is an option to be considered?

I don't know why you would say that.  You got: biting, sarcastic comedy the actual answer that you and everyone else suspected was the case opinion slightly related to the original topic and all at no extra charge  :D

One more question: I have two boxes in failover config. Will there be any problems if one is running Nano while the other is on Regular? Thanks so much for the help!

Thanks a ton jimp, was worried about that one. :) Greets

Hello. Today I launched the new 2.3.3 upgrade and it was successfuly. Thank you at all.

Sorry for the late reply, I was able to convince my wife to allowing to move the pfSense box behind the modem.  Everything is working well and look forward to starting the rest of my project.  Thank you all for your input.

So I thought might be cable as well, I swapped all the cables that where connected to NAS and also tried new switch no changes. I will try new cable on the modem right now cause that is something I should have tried. Thank you for the input thus far :)

@KalanVryce: Ok…. so just as an FYI if anyone else has this issue I was able to resolve it by choosing the "Reset to factory defaults" option a fresh install and several reloads didn't resolve it but out of curiosity I gave it a try and it worked... why I don't know but perhaps a bug in 2.3.2 ISO? It didn't work for me. Exact same issue. Reset to factory gives same result, but thanks for sharing!

@doktornotor: Get a switch? Get a crossover cable? Get a working cable? Get a crystal ball? Got a switch. No change Don't have a crossover cable, but I have a switch that works. Working cable? Wouldn't get an IP assigned on LAN client if cable didn't work. Swapped anyway. Same result. Crystal ball. Working on it.