Known issue, see https://redmine.pfsense.org/issues/2495

Solved! It was actually what you, stephenw10,  suggested, TP-cables!! I changed both cables, restartet the Cable modem and Alix. Bang! Full speed again..even if if test it several times :-) (testing with nettfart.no) 66-70.3 Mbit/s 10.81 Mbit/s 4 ms Ping Thank you so much for helping me research this issue!!! For info: Alix 2D13 = been running for 1.5 years. PC = just a couple of days.. ;) Same fault appeared on Alix 2D13, with both pfSense 2.0.x and 2.1. Using Alix 2D13, pfSense 2.1, and downloading a 1Gb file.. the Alix used 25-31% CPU.

Any one ?

Are these network printers? If not then you need to run a print server such as CUPS. I think there's some information in the docs subforum about doing that but it's not supported in any way. Steve

thanks mate!

What you probably need is SNORT as IDS/IPS. I never used it but it is a detrusion prevention and detection system which allows you to block source or destination IP addresses to be blocked if there is any violation. Blocking can be done by time so that an IP/host will be blocked for 1h and after that can again access and of course - if there is violation again - blocks again this IP/host. Of packages forum there are some threads about snort and some really good threads and how-tos from user bmeeks how to use snort. You should have a lookt at this and reads the threads carefully to find what you need.

@jimp: On 2.1, if you enable the option to kill states when a gateway goes down, then all states are removed when a gateway goes down, not just the WAN-side states. Enable means checkbox is not selected, right? It seems I'm observing the same issue - I have this ckeckbox unticked and my server was not able to register to the external voip provider until I manually cleared the states through web gui.

No ideas?!

@johnpoz: Here is doc https://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots Not sure how updated it is..  But gives you the general idea. I run my pfsense on vm, so rollback is click click – just click on take snapsnot of the vm before I do anything.  But if running hardware - just have install media ready and copy of your config before you do anything.  Worse case you reinstall and restore you config and bing bang zoom your back to how you were in a a couple of minutes. What exactly are you running pfsense on - is there some specific reason your running amd64?  And not i386 -- there seems to be far less issue when running i386.. Unless your running lots of ram not sure what advantages 64bit has to be honest. Thanks for the link, John, I will study it  ;D The system backup/restore was how I reinstalled 2.0.3 two weeks ago. But that didn't quite work. I think I understand the logic; the restore simply plays all changes ever made to the system again, as a sort of 'macro'. At least, from looking at what it did this is my conclusion, as I saw it installing snort, deinstalling snort, installing snort, deinstalling snort, and so on for all packages. The end result after some hours was a system that still didn't work, so in the end I did a clean install of 2.0.3, all the packages, and all customizations for all packages. The upgrade from 2.0.3 to 2.1 on the other had worked 100% the first time  :P My hardware is in my sig. It has been recommended to me by a very kind and great person, who was helped me tremendously during the pre-move to Pfsense, by explaining things, recommending hardware, troubleshooting my ISP-problems. And to this very day, he still refuses to let me pay him some money so he can take a cup of coffee on my behalf :-\ (Yes you know him, he is on this board very regularly  ;D). I have AMD64 since I have 8 gig of ram. I have created a screenshot of my dashboard and attached that. Now I am off trying to find out why FreeBSD (desktop) doesn't want to see my LAN (samba is installed)  :-[ Bye, [image: STATUS.jpg] [image: STATUS.jpg_thumb]

I wasn't testing correctly. Communication does work. Thanks to everyone for help.

Ah, the boxes ability to see packages is certainly proof it has internet access but there are a few things that can prevent that whilst general internet is working. Try the Diagnostics: Ping: page instead. Pinging from the console command line gives an even better result as it uses the system routing table instead of specifying a gateway. Steve

Excellent, I'll try that tonight. I'm also doing a temporary measure by using NX and going to setup a VM to come in and pull up a remote desktop. I'll post results and what I did when I get this done. Thanks!

Do you want full on SNMP monitoring.. Otherwise you have your State table size  on the main page, but that isnt a real time updated graph, you have to refresh it, Show states

I restarted my firewall from scratch and it sorted itself out. Most strange.

After having tried this on my production hardware also I have unfortunately concluded that is isn't limited to virtualized instances of pfSense. My now live physical firewall does the same thing (ntp service crashes) when having it's ntp server peers on two different interfaces (WAN and LAN). :'( Only using external ntp servers on the WAN interface have been stable for a few days now so that is the workaround I 'll have to settle with until the bug is resolved. Only connecting to the internal ntp server on the LAN interface is not an option for me for redundancy reasons, so I haven't tried that but my guess is that it would also work. Maybe it isn't very common to have ntp server peers on multiple interfaces and maybe that is the reason this haven't been discovered in beta testing?

There is a possible gotcha when setting up your DSL modem as a bridge - you usually need to release your public IP address BEFORE configuring your modem to bridge mode. Here's a good article on how to do what you are wanting to do: http://forums.macrumors.com/showthread.php?t=579876