Will add this setting - thanks very much!

Here is a free one for windows that I have used in the past http://www.snmpsoft.com/syslogwatcher/syslog-server.html Pretty simple to use.

Since you just made an adjustment to the firewall, I suspect you may be just seeing leftover connections that lost their states. They should go away on their own, but you can try rebooting your clients, then the firewall, to see if that clears it up. More here: https://doc.pfsense.org/index.php/Logs_show_%22blocked%22_for_traffic_from_a_legitimate_connection,_why%3F @MaxPF: No other options were changed and up till 1 hour ago this was not happening. Is there a way to disable this behavior? On the WAN I only want to see the incoming traffic blocked. When you say "see" do you mean disable logging for the default rule? https://doc.pfsense.org/index.php/Firewall_Logs#Disable_Default_Block_Logging

I agree with Jon here. You are using the Cisco switch to replace four unmanaged switches. You are using VLANs internally in the switch to separate it into what is effectively four discrete switches. This should mean that there are no tagged packets entering or exiting the switch and there is no VLAN setup required in pfSense. This has the advantage that you can move ports on the switch between subnets just using a config change and that it's easy to add VLAN interfaces in pfSense if you ever need more than 6. The disadvantages of such a setup are that everything has to be in one physical location (probably not a problem for you) and that it's very easy to get the switch config wrong resulting in ports on the wrong group or communication between the subnets. Steve

Already been through these? https://forum.pfsense.org/index.php?topic=56766.0 https://forum.pfsense.org/index.php?topic=69807.0 https://www.google.com/search?q=pfsense+screensaver

you give me home my friend. I learned networking from the internet and a few trial and errors until i found myself working a wireless networking like Ptp, and PtMp. I have the definitive guide downloaded and have interacted with some guys here. Okay…I'll take that chances!

thank you guys, you are the best. it's working now thank to your knowledge.

Problem solved.  Proxy configuration.  Since I'm running on an APU4, I'm running nanobsd.  Since I'm running nanobsd, I have Hard Disk Cache set to Null (i.e. no disk cache).  I had values in some of the variables specifically dealing with disk cache.  I figured it was a moot point because my Hard Disk Cache was set to Null.  It looks like these values were causing Squid to think there was disk cache, and when it tried to retrieve it, nothing was there and I got the error.  I changed the settings such that Squid would only ever look to memory for cache et voila!  It works great.

@DemoNIck: Any packet loss appearing on the graphs is ONLY due to p2p traffic. Now I am almost certain that this "packet loss" has nothing to do with the pfSense system itself Excellent. I suspected this was the case. Now some simple traffic shaping ought to tidy things up so that your high priority traffic isn't impacted. @DemoNIck: But before we do so could you be so kind and be more specific on the "WAN saturation" indication. I apologize for not writing more clearly. I have a bad habit of thinking faster than I type.  ;) By "WAN saturation" I meant the outbound bandwidth utilization on the WAN link reaching or near 100% [due to p2p traffic]. It has been my experience that retail WAN technology (POTS, DSL, Cable, etc.) is subject to extreme performance degradation (i.e. packet loss, etc.) under high bandwidth utilization conditions. When sustained bandwidth utilization exceeds 80% then smaller traffic bursts start hitting the "artificial" bandwidth limit imposed the Internet service provider (ISP). When traffic hits that artificial limit, the ISP begin to "rate limit" the traffic. Often their rate limiting is very "brute force" by simply discarding packets thus creating all sorts of timeouts and retransmits. Although you never specifically mentioned the bandwidth of your connections, I know from experience that most Internet connections are asynchronous and so are highly sensitive to outbound traffic (i.e. p2p). Your WAN traffic graph shows periods of intense outbound bandwidth utilization with "wan-out-pass" reaching 742kb/s which is at the limit of the most common outbound speed (768kbps) so WAN outbound bandwidth utilization became the primary suspect especially since the rest of the graphs have values in reasonable ranges. @DemoNIck: Once again thank you in advance for your time and effort. It's been my pleasure. Thank you for creating an interesting topic.

@Derelict: There is an easy way.  Use a switch. Thanks. I'm extremely grateful for all of your advice. The kind people on this forum have been phenomenal.

Why such an old version?

Diagnostics->Backup/Restore ??