@ krzee
What could one do, if say, in your particular example "client1 with lan 10.10.1.0" has an IP in that LAN like 10.10.1.120 and that is allocated to a bridged interface, as this client1 is a hypervisor for 5 VMs that are also members of the 10.10.1.0 lan ?
In my case:
root@client1:/home# route -een
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface MSS Window irtt
0.0.0.0 WAN_GW 0.0.0.0 UG 0 0 0 eth0 0 0 0
10.8.0.0 10.8.0.5 255.255.255.0 UG 0 0 0 tun0 0 0 0
10.8.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 0 0 0
10.10.1.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0 0 0 0
WAN WAN_GW 255.255.255.224 UG 0 0 0 eth0 0 0 0
WAN 0.0.0.0 255.255.255.224 U 0 0 0 eth0 0 0 0
After following your example, I ended up with:
root@client1:/home# route -een
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface MSS Window irtt
0.0.0.0 WAN_GW 0.0.0.0 UG 0 0 0 eth0 0 0 0
10.8.0.0 10.8.0.5 255.255.255.0 UG 0 0 0 tun0 0 0 0
10.8.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 0 0 0
10.10.1.0 10.8.0.5 255.255.255.0 UG 0 0 0 tun0 0 0 0
10.10.1.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0 0 0 0
WAN WAN_GW 255.255.255.224 UG 0 0 0 eth0 0 0 0
WAN 0.0.0.0 255.255.255.224 U 0 0 0 eth0 0 0 0
Which obviously made my virtual machines inaccessible...
I know there's a fix for this as I saw this setup before somehwere, but I was curios what would you suggest.
Many many thanks for your comprehensive tutorial.
Cheers.