Voodle wrote:
That's probably not quite right, I'm using an IPSec VPN to one router, that connects to another router - I haven't tried it with the one LAN connected to a different subnet using static routes though.
Something that might be worth trying would be to put the LAN to LAN VPN as the default route, that way you can be certain that's going to route through - something to consider is that the other end also needs to be aware that traffic for that LAN has to go through a specific gateway as well.
I think it's more of an implementation thing on the Draytek. The tunnel is only negotiating the subnet specified on the main page, not the additional ones on the "More" page. Routing appears to be okay, because the routes do get added. I'm guessing that you're only specifying a single subnet at the Draytek end, even if that subnet effectively supernets the multiple subnets that sit behind the VPN at the other end. For instance, if I tell the Draytek to just set the VPN to 10.0.0.0/8 then everything works fine. The reason I can't do that is that the VPN server at the other end doesn't then like the fact that the subnet at my end overlaps with that network range, so I need to state the specific subnets on the Draytek.
