You could put pfsense in a bridge with filtering turned off and some of the packages mentioned in the link. I am not sure if they work on the bridge interface or LAN/WAN or if at all. But it is worth a shot.

A transparent proxy is invisible for all intents and purposes to the client You could log all traffic, but when it is encrypted you will just see a garbled mess You will not be able to see encrypted traffic without modifying the clients

A 1gb port can do 1gb both ways, which is 2gb/s.

http://www.newegg.com/Product/Product.aspx?Item=N82E16833704011 These are the cards I put in

@stephenw10: Good to know. Did this start happening immediately when you installed the Squid3 package then or maybe after some package update. You could use the Squid2 package instead, that is supported by the devs and this sort of issue would be a show stopper. Steve no.. i think it takes at least 1 month or 2 after squid installation. atm we use handycafe filter to block porn sites, etc. so pfsense handles only for policy routing, firewall, ntp server, dhcp server

That's great advice.  I'll see if I can get  capture during an outage. Jeff

Thanks for your answer. The main problem is that i want to recieve the notification form the pfSense firewall itself (under System -> Advanced -> Noticfication) so there is no interface that the traffic enter. Of course i could change my VPN Tunnel that it is not the default Gateway, but i hope there is another way. //EDIT My VPN Priovider whitelisted my needed SMTP Servers… It works  - done!

openvpn  / ipsec vpn are builtin vpn solutions that are generally used for any form of remote access.

Not forgetting that, normally, syslog runs on UDP.  If anything is corrupted it will be just discarded.  Have you checked for errors on the network between machines? Edit:  Or maybe run a packet capture to see if pfSense is actually sending them?

@charliem: Generally this is caused by something sending data to the serial port while getty is running.  getty is expecting nothing but username/password pairs but seeing 'garbage' from your console switch.  This is  a unix thing, not a pfSense thing … I can't speak to the apparently successful logins shown in your logs.  Are you saying the logins are false positives, and you didn't really log in at those times? that is correct…i am NOT trying to login at any of those times, and NO ONE knows my password except myself, and console access from the outside is not allowed. since i unplugged my console switch....nada.... i will look into the console switch config...

Yes, fixed my problem. haven't had to reboot since. Thank you!

I think I figured out the errors reported on my switch. I enabled EEE on my switch and it seems my Intel i350 is the only NIC that actually supports EEE. There seems to be a correlation between my error count incrementing and the ports being idle. This would explain why I saw a few errors on my ports shortly after restarting PFSense from the upgrade, no traffic. Recently, my ISP did an upgrade late at night, and my switched showed the ports going up an down a few times because they turn off when no traffic and an EEE device is plugged in. The next morning, I saw 2 more errors. I can't get a causational link, but it seems highly correlated. Even after 9 days of uptime, I only have 5 total errors and they were only spotted shortly after something would have caused WAN traffic to cease.