[NTLUG:Discuss] pass all packets between two nics

[Kenneth Loafman]

Jack Snodgrass wrote:
> On Wed, 04 Jun 2003 22:38:11 -0500, severia wrote:
> 
>>>So... you make a VPN connection from your home to work and get a
>>>172.16.14.x address assigned to your home machine. You have a
>>>secure, encrypted tunnel set up.
>>
>>    Well, that is pretty neat.  I wondered how I was going to address the 
>>machine at work.  I did not realize that the home machine would get an IP 
>>address.  That means the home machine would have two IP addresses.  One I 
>>assign with the VPN and whatever their ISP or local lan gave them 
>>normally.  Do I understand that correctly and is it a problem?
> 
> that's it. Your home box will have both a real, ISP assigned Address
> and a private, VPN assigned Address. The VPN client will setup routes
> for your private network to go via your VPN interface. So... if you 
> ping www.yahoo.com for instance, you'll go via your ISP and use your
> ISPs address. If you ping your WindowsA machine, you'll go via your 
> VPN connection to your private network. The VPN connection will encrypt
> the packet that is going to go over your VPN and it will then send it 
> to your VPN server over the internet using the public IP Addresses. 

One question about the above scenario.  When I worked at Sabre and used 
VPN to access their local network, all internet connections went via 
VPN, including browsing, ftp, and so on.  So when you went to some site 
and forgot about your VPN connection, the work systems were still 
logging your activity.  That's not good for separating your work and 
private lives.

Is that problem still in VPN connections, or was there something we 
needed to unset to get the system to not use VPN for everything?

It would be handy to use VPN (ssh is somewhat limited), but not at the 
cost of user privacy when at home.

...Ken