Removal of LAGG
-
Must be failing fairly regularly then!
-
Depends how you are using it. If they are in a group you're policy routing to (which I think they are) then pf will will load-balance between them so you will see connections change continually.
-
They are inna group and they do appear o load share but only seems to be 3 of them at any one time for some reason.
-
Are they all connected? Are they all at the same tier?
-
@stephenw10 Yes, they are all connected and all at tier 1
-
Hmm, well I would expect to see traffic on all of them then. One thing that often causes issues in this sort of setup though is when the VPN provider uses the same gateway IP for multiple servers. In that situation pf can only route to one of them.
-
Yes, that's a problem with Nordvpn, which is why I also use PIA also. Consequently, I have only one instance of Nordvpn and the rest are PIA, which have different gateways
-
One issue I have found but may not be related to VPNs is that on running a DNS leak test, I find my ISPs external WAN ip address alongside the VPNs public ip address. The dashboard shows the only DNS server as 127.0.0.1, which I believe is correct as I am using DND resolver. Had a look around the forum at the many posts but yet to find a cause or solution!
-
How is Unbound configured? How is DNS set in System General Setup?
-
-
OK so you have Unbound set to use any (all) interfaces for outgoing queries and that includes WAN. Since it's resolving directly anything looking for that will see the WAN IP as the source.
-
So, I assume I need to remove WAN from that then.
-
No matter what I do to the outgoing network interface i.e. leave it at WAN only, I still get the ISP ip address showing in the leak test. I thought it would just show 127.0.0.1
-
The leak test shows the IPs of the DNS resolver in use. Since you are using Unbound directly it will show your public WAN IP address for any queries sent out of the WAN.
If you set Unbound to use only the VPN connections for outbound queries the leak test will only show the VPN provider. That might cause problems for any service that uses DNS checks, like Netflix for example.
