pfSense 2.5 VPN-Killswitch gets hammered
-
Noticed something weird, fresh install of pfsense 2.5 with some OVPN-Clients. I made a VPN-Killswitch via tagging. But after a reboot and all Clients were up again, something was hitting the killswitch all the time. Even after restarting every client (again).
I then activated "Reset all states if WAN IP Address changes" and rebooted and the problem was gone. Although I don't think that this option is related to that problem...
Never had this happened to me like this in 2.4. -
Maybe it is related to Hyper-V, SR-IOV and a new NIC that I am using and has nothing to do with the new pfSense version.
-
Meanwhile I had to disable SR-IOV, but the problem persist.
It is now past half an hour and still there is one connection hammering into the "VPN-KillSwitch", although the tunnels are all well and up.
Is this the "fault" of pfSense or the program on that host, that is doing this? Can I kill states with that rule? Probably not, because it is just a floating rule rejecting tagged connections outgoing on WAN?
I killed that state manually but there is no way doing this automatically? -
@bob-dig How about checking what get's blocked by that rule and where it comes from? Do a state table lookup and see what's running against that rule?
-
@jegr Hey JeGr, it seems to be a p2p-filesharing-application and or dns. I use 8.8.8.8 as the default dns for several interfaces.
Because I couldn't stop it happening, I enables "Do not create rules when gateway is down" in the advanced settings and created reject rules as necessary. Now I have a clean log at least...
