Many thanks! I found some good videos on youtube. I probably should look more often there. :) https://www.youtube.com/watch?v=xpXhudbsrr8 is a 3h introduction by a Microsoft guy into networking. There also is a (right now) 7-part introduction to pfSense, that is also quite good, though it is a little more of a reference video, going through all web-ui options one by one.

So you have pfsense running on this 2k16 box.  So pfsense wan is the interface that is exposed to the internet right? The setup openvpn on pfsense, vpn in and then you would have access to anything behind pfsense

Excellent. Thank you.

Nov 29 21:31:21 dpinger WAN_DHCP 99.233.16.1: Alarm latency 19857us stddev 24963us loss 22% Dunno, but 20+% packet loss is considered a down connection with dpinger default settings. You are having real issues with your ISP, it's not something that pfSense would be inventing. So yeah, disabling GW monitoring won't help obviously, the packets will still get lost and things won't work.

Thanx Is it correct when LAN-loadbalancing rule is on top, both gateways are used at the same time? The failover rules only starts when laodbalancing failes due to one missing WAN connection? The way I see it there is no way to set one gateway as default, and when that one is "full use", the next gateway takes over? I've set weight on both gateways, but still I switch between both WAN. The reason why I would like WAN1 to be default is because it has lower latency than WAN2. Other than that it works perfect  :)

I don't know how, but now all works fine. All what has been changed - removed swap for increasing / - my / is overfilled (free 1% or 9 MB). Now used 73% and PPP connection up and works fine

Well, it's now solved. Wasn't pfSense at all. Rather, ESET was screwing everything up. Only found this out through trial-and-error reinstall. Apparently, it simply does not like when a network is set as 'Home', but with a public network it all works. Obviously with a public network sharing becomes a hassle so… Anyway, back to writing up the paper  ::)

OMFG ! I am so tired I didn't correctly read the error message, thinking that this IP replied instead of the reply saying that my IP isn't allowed. Fixed auth, and here we go ! I feel stupid for the lame post. Thanks for the tap behind the head John :)

In my case, reboot always temporarely restore the network functionality. Does this apply to you as well? At the moment I've followed some suggestion from the thread on the FreeBSD forum and forced the network card to run at 100Mbit instead of 1Gbit. So far so good. I'm at 24 hours with no issues. Knock on wood! Franco

Dok – maybe we are just behind the times and have not gotten our telepathic skills enabled yet.. Is there something we need to eat/drink to get these skills?  Maybe we using the wrong font and not seeing the detailed information?  Maybe the actual details of what is done is hidden in code?

I generally use search on the menu bar then advanced search. I would limit the forums to Packages and Packages > Cache/Proxy if you are looking for info about squid.

Amen. Keep it simple then add technologies one at a time if you want to experiment. But then when you are posting on a forum you are not asking someone for help with an LACP problem to solve what is really a basic issue. People get too wrapped up in configuring too many things at ones. Eg. If you are going to do 20 VLANs, do one and get it working right first.

You'll see messages like these… Alarm messages mean it's going into an alarm state, clear is coming out of one. Dec 6 10:01:59 dpinger WANGW 198.51.100.1: Alarm latency 710us stddev 620us loss 22% Dec 6 10:04:41 dpinger WANGW 198.51.100.1: Clear latency 765us stddev 741us loss 5% Dec 6 10:09:54 dpinger WANGW 198.51.100.1: Alarm latency 605us stddev 633us loss 22% Dec 6 10:12:17 dpinger WANGW 198.51.100.1: Clear latency 747us stddev 648us loss 5% Dec 9 10:49:20 dpinger WAN_PPP2_PPPOE 10.6.220.1: Alarm latency 1046us stddev 2398us loss 22%

I could be wrong but I don't think that Squid can cache something that it cannot read because of the encryption.