When I have client 1-5 all connected to 5 different VPN servers with the default settings on a fresh install, what exactly is the behavior?
For me it appears to randomly direct all my devices to one of the VPN servers at random.
ip rule
for ID in 254 111 112 113 114 115;do echo "Table "$ID;ip route show table $ID | grep -E "default|^128|^0";done
I have all VPNs connected but Redirect Internet traffic to "No" on all of them. I just disconnected and reconnected them all and all traffic goes strait out the WAN until I hit apply on one of the VPN configs so it seems like the behavior is the last VPN config you hit apply on?If however, 'Redirect Internet traffic=ALL', then the selective routing will depend on which VPN Client connection is enabled/ACTIVE last and may be the cause of the seemingly random selective routing you have described.
Does this mean I can use Policy Rules or Policy Rules strict and turn the kill switch only on VPN config 5 to have backups leading to a final failure?If ALL 5 VPN clients have Selective Routing enabled ('Redirect Internet traffic=Policy Rules*'), then if there are overlapping source IP ranges defined for Selective Routing, then for routing decisions, VPN Client 1 will have the highest priority with VPN Client 5 having the lowest priority.
I am getting an error on the command "ip rules" or was this just the title of the next command? The output I get is:NOTE: CPU affinity has no bearing on the routing rules, but can affect VPN tunnel throughput performance.
Unless you're also running a Dual-WAN environment, the Policy routing rules are always static and are processed in descending order of priority.
I suggest you verify/check the Routing Policy rules and routes:
Code:ip rules for ID in 254 111 112 113 114 115;do echo "Table "$ID;ip route show table $ID | grep -E "default|^128|^0";done
Table 254
0.0.0.0/1 via 10.8.2.1 dev tun14
default via **my ISP** dev eth0
128.0.0.0/1 via 10.8.2.1 dev tun14
Table 111
Table 112
Table 113
Table 114
Table 115
I have all VPNs connected but Redirect Internet traffic to "No" on all of them. I just disconnected and reconnected them all and all traffic goes strait out the WAN until I hit apply on one of the VPN configs so it seems like the behavior is the last VPN config you hit apply on?
YesDoes this mean I can use Policy Rules or Policy Rules strict and turn the kill switch only on VPN config 5 to have backups leading to a final failure?
Abject apologies, I have corrected the silly typo in the command[/QUOTE]I am getting an error on the command "ip rules"
Correct - 'Redirect Internet Traffic=No' doesn't do what you would expect....it is the same as 'Redirect Internet Traffic=ALL'
This might be more obvious if you read this setting as "Force Internet traffic redirection" perhaps. I should perhaps reword it that way.
I can't quite understand this, is there a simple example to show the difference between strict mode and regular policy mode, what is an example of a rule "not specifically" targeting a tunnel interface?in strict mode,
only rules that specifically target the tunnel's
interface will be used. This ensures that you don't
leak traffic
I think adding the word Force makes a lot of sense. Makes me wonder, theoretically could a VPN provider selectively not encrypt certain traffic?
Online somewhere they recommended routing the default gateway/router IP to WAN for better performance... but I don't really understand what that means?
"A common configuration setup where you want your whole LAN to go through the VPN, but not the router itself:"
LAN 192.168.1.0/24 0.0.0.0 VPN
Router 192.168.1.1 0.0.0.0 WAN
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!