@johnpoz said in Cloudflare:443 in fw log...: just personally block all traffic to 1.1.1.1 Floating rule, out WAN, quick, source any/any destination 1.1.1.1/any? Thanks

Yeah, it shows the current link. You can see the available link types the NIC supports in the speed/duplex drop down in the interface config. Or ifconfig -vm igc0 at the command line. Steve

OpenVPN is UDP by default so port tests against it will fail. I upvoted enough of you posts to get your 'rep' above 5. You should avoid the spam filter now. Anyway, glad you're up and running.

That's just the address the management page is using to access it for stats. Squid can listen on any interface IP it's configured for. In transparent mode it uses localhost like that and port forwards redirect traffic to it. You should still be able to access it directly on the interface IPs though. Steve

@stephenw10 thank you I was looking at WPAD right now. i hope everything will be fine

@stephenw10 Thank you for pointing out that my firewall is generating a lot of logs. I have checked firewall logs and found out that my home assistant is causing the problem. Because I have configure DoH blocking in pfblocker, and this is what being triggered. I have disabled the logging for this and that fixed the problem. Again thank you so much for the big help.

Can you just swap the LAN/WAN ports in the Interface assignments (and the cables) and see if the problem follows the swap?

Ok, so that's policy based IPSec (tunnel mode) at the pfSense end. I'm not familiar enough with PA to know if that screen confirms route vase there. It does appear to have tunnel interfaces which implies it might. The P2 policy you have configured there is only carrying traffic between the LAN subnet(10.3.93.X) and 192.168.5.0/24. Which means it isn't carrying traffic between 192.168.5.102 and 8.8.8.8 for example. I would confirm the PA is using route based IPSec and then switch pfSense to match. That way you can route whatever traffic you want across the tunnel. Otherwise you have to do this: https://docs.netgate.com/pfsense/en/latest/recipes/ipsec-s2s-route-internet-traffic.html And that can be inconvenient because it often over-matches and pulls traffic over the tunnel you do not want to be. Steve

@stephenw10 said in alias-subnet: It's the default value for a DHCP Alias IPv4 address. It gets saved in the config if you save a change to the WAN but does nothing unless you actually have an alias IP address in there too. [image: 1651758786050-screenshot-from-2022-05-05-14-51-27.png] Steve hello Stephenw10, Thank you very much for the quick reply. I wish you a good day.

@empbilly I don't know if you've tried this yet or not, but in the DHCP Leases page under the Status menu, you can easily (with a couple of clicks) add machines to the WOL list by clicking the little blue plus button in the Action column.

@maddy_in65 From what you've posted it seems like only outbound traffic to port 80 from the problem VLAN is failing. Maybe run grep ' 80 ' /tmp/rules.debug and look for something other than the standard "anti-lockout rule"?

Yes, if both those pfSense instances are running an otherwise default config that will work fine. So if it's not it's because of something you have changed. Firewall rules? Outbound NAT rules? WANs still using DHCP? Steve

Thank you @stephenw10 and @johnpoz this looks like it is working now. I assigned only one pool to NTP and now reach column shows 377 for four servers. So this is golden. Thanks again!

@stephenw10 Thanks, Steve. I reinstalled Snort and turned off blocking. So far, everything appears to be working fine. Bert

Yes I added the lines in the config. The PPP connection was established without problem and there are no errors in the log file. I haven't had outage since than, therefore I couldn't test the reconnect part.

In the end I wrote a very tiny shell script to check the ZFS status and put it into /usr/local/libexec/nagios/check_zfs_status.sh #!/bin/sh cmdzpool="/sbin/zpool" healthcheck=`$cmdzpool status -x | grep -c "all pools are healthy"` if [ $healthcheck -eq 1 ] then echo "ZFS Volumes OK" return 0 else echo "ZFS Volumes error." return 2 fi It's not the ideal solution since the check has to be installed manually but it's better than nothing.

Ah it dawns on me there is one thing I should mention so someone else doesn't get caught. ARP cache played a huge part in this and an accidentally left over rule in one of the firewalls as well. The firewalls were basically competing to be the gateway so things would get weird like a vm would boot up with a gw then a while later change to another. Once ARP cleared up, everything was fine.

Yes that should be fine but neither reached the speeds you were seeing to speedtest so it doesn't really give us any more information. If you can connect the pfSense WAN to something running an iperf server directly and test to that it removes any sort of restriction reaching it so any limitation left much be in one of the pfSense interfaces. As I said I do that sort of test all the time using another pfSense instance on the WAN. That way it hands out DHCP so the test device just works. Steve

@johnpoz I block doubleclick also they have some bad bugs in that system. I am glad to see I am not the only one.

Thanks guys for your answers!