Re: [Openvpn-users] Re: LAN gaming over openVPN

["Erik Anderson" <erikba@xxxxxxxxxxxxxxxxx>]

I see some _potential_ confusion as to what ip addresses mean on a VPN.

(Are you trying to not only connect not just two machines together, but all 
the computers that are on the same network "behind" either machine?  If so, 
disregard the rest of this message...)

A VPN connection is almost like someone installing a second network card in 
your computer.  Being connected to the VPN means that your computer has two 
"network cables" that it can talk through, and two identities (one for each 
network).  The "vpn cable" on the client machine connects to the back of the 
server machine (in a TUN network), or into the same hub that the server 
machine is plugged into (in a TAP network)

This is what a TAP network could look like:

Server machine:
 BRIDGED network (both cards have the same identity): 192.168.1.2
Client machine
 normal network: 192.168.0.2
 vpn network: 192.168.1.3 (same subnet as server, different address)
in this instance your ifconfig line would be in the 192.168.1.x subnet, and 
would be careful not to assign any ip addresses that the cable/dsl router on 
your server network might assign.  or drop the line and have the cable/dsl 
router field all requests from machines on the vpn

This is what a TUN network could look like:

Server machine:
 normal network: 192.168.1.2
 vpn network: 192.168.3.1
Client machine:
 normal network: 192.168.0.2
 vpn network: 192.168.3.3
In this instance you should be using a tun-style network.

----- Original Message ----- 
From: "Oliver Wittkopf" <oliver.wittkopf@xxxxxxxx>
To: <openvpn-users@xxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, December 01, 2004 2:54 PM
Subject: [Openvpn-users] Re: LAN gaming over openVPN


> i also tried to establish some routs...
> does i have to change the subnetsmasks of the virtual ip adresses?
>
> i tried this:
>
> Server (192.168.1.2, 255.255.255.0; 192.168.3.1, 255.255.0.0):
> route add 192.168.0.0   mask 255.255.255.0   192.168.3.1
> route add 192.168.0.255 mask 255.255.255.255 192.168.3.1
>
> Client(192.168.0.2, 255.255.255.0; 192.168.3.3, 255.255.0.0):
> route add 192.168.1.0   mask 255.255.255.0   192.168.3.3
> route add 192.168.1.255 mask 255.255.255.255 192.168.3.3
>
>
> in fact, can you say me what's wrong?
>
>
>
> > To get to all IPs assigned to a system you must use routing.  There is
> > no other option.
> >
> > Attempting to use TAP and routing, IMHO, would be a nightmare. Without an 
> > in-depth knowledge of routing, and bridging you would be
> > forever in danger of it breaking at the wrong time...
> >
> > Determine what you need broadcasts for and put in a non-broadcast
> > solution and use TUN.  As an example use WINS for netbios name
> > resolution.
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/openvpn-users


____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users