[Gllug] Right way to route some traffic to a VPN connection

[Martyn Drake]

What Stephen says makes sense.  You must forgive me, I've taken the 
lazy route of having the default gateway also being the VPN server so 
that it does all the routing between LANs automatically.

Regards,

	Martyn

John Winters wrote:
> A dedicated box on the local LAN acts as the VPN gateway.  This is not
> the same box as the normal default gateway.  The other machines on the
> LAN need to know somehow that packets intended for the remote end of the
> VPN are to go to this dedicated box and not to the normal default
> gateway.
> 
> The question is just whether they should be given this information by
> the DHCP server, or by the default gateway redirecting their packets.
> 
> John
> 
> On Thu, 2005-05-19 at 11:50 +0100, Martyn Drake wrote:
> 
>>How is the VPN connection set-up?  Does the machine/router not route 
>>accordingly for the internal LAN so that selected (or all) machines on 
>>your LAN can route packets for the particular set of IPs on the remote 
>>LAN side?
>>
>>Or am I talking complete gibberish here?
>>
>>Regards,
>>
>>	Martyn
>>
>>John Winters wrote:
>>
>>>I have a LAN which has a permanent connection to the 'net, plus a VPN
>>>connection to another LAN.  IP addresses on the local LAN are allocated
>>>by DHCP.  What is the correct way to tell the machines on the LAN to use
>>>one machine as their default gateway and another (the one which handles
>>>the VPN connection) for packets for one particular range of IP
>>>addresses?
>>>
>>>Method 1 - include information for both in the DHCP server (and if so,
>>>how?)
>>>
>>>Method 2 - just set up the default route by DHCP, then have the default
>>>gateway issue redirects to client boxes as the need arises.  (and if so,
>>>does the gateway need any particular setting up?)
>>>
>>>TIA,
>>>John
>>>
> 
> 
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug