On Thu, 26 Jan 2006, Raúl Alexis Betancort Santana wrote: > Branch1: > Lan: 192.168.0.0/24 > Central: > Lan: 192.168.100.0/24 > Branch2: > Lan: 192.168.2.0/24
Last time I had such problems, I created one tunnel per network prefix. It was needed because the VPN gateways we were using (D-Link DI-808HV) are basically broken crap and cannot route worth anything: it would not route per more specific prefix (besides other bugs). > I've tryed to put a /16 mask on the tunnel "remote network mask" param of the > Vigor "LAN-to-LAN VPN Config", but in that case, any traffic goes or comes > from the tunnel, and I don't know how to use the option that says .. "Use Yes, this is the same routing bug the D-Link has. Just return the units to wherever you bought them as the defective crap they are. Try to find an embedded linux or embedded BSD-based VPN gateway, at least it will know how to route. > this tunnel as default conection", because if I activate it, then I could not > access the branch's router by it's public internet IP. It is the same routing bug. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
