[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] Addressing weirdness in routing mode: Solved!


  • Subject: Re: [Openvpn-users] Addressing weirdness in routing mode: Solved!
  • From: "BlaaT 0001" <blaat0001@xxxxxxxxx>
  • Date: Thu, 13 Apr 2006 11:31:17 +0200

Darn, forgot the CC the list again.....sorry all.

On 4/13/06, BlaaT 0001 <blaat0001@xxxxxxxxx> wrote:
> Hello Paul,
>
> I would recommend _not_ using this method as well. The routes you
> spoke of before are used by OpenVPN to communicatie with the TUN/TAP
> nic.
>
> Instead try using these settings:
>
> in the server config file:
> "server 10.127.250.0 255.255.255.0"
>
> in the client config file:
> "client"
>
> That's it. This would give the OpenVPN server an IP of 10.127.250.1
> All the clients would communicate with the server using the IP:
> (My_OpenVPN_IP minus 1)
>
> This is due to a limitation of the TUN/TAP implementation on Windows.
> OpenVPN 2.1 currently in beta uses a new updated driver (version 8.2)
> of the TUN/TAP nic with does not have this limitiation. This
> limitation involves the NIC only being able to communicate with the
> adjecent IP (10.127.250.5 is adjecent to 10.127.250.6).
>
> What OpenVPN does is claim the subnet 10.127.250.4/30 (10.127.250.4 -
> 10.127.250.7, with 4 being the netid and 7 being the broadcast address
> that leaves only two usable addresses, a point-to-point connection)
> for the client to use.
>
> That's why OpenVPN creates the routes you spoke of.
>
> Cheers,
>
> BlaaT
>
>
> On 4/13/06, Erich Titl <erich.titl@xxxxxxxx> wrote:
> > Paul
> >
> > Wright, Paul wrote:
> > ..
> > >
> > > At any rate, I solved the problem by removing the following statement
> > > from the config:
> > >
> > > Server 10.127.250.0 255.255.255.0
> > >
> > > And replaced it with
> > >
> > > Ifconfig 10.127.250.1 10.127.250.2  (on the server side)  and
> > >
> > > Ifconfig 10.127.250.2 10.127.250.1  (on the client side)
> > >
> > > Then everything was happy!
> >
> > I would suggest _not_ doing this, the routing applied with the server
> > directive is the canonical behaviour of OpenVPN. Look at the server
> > directive in the manual pages.
> >
> > cheers
> >
> > Erich
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> > that extends applications into web and mobile media. Attend the live webcast
> > and join the prime developer group breaking into this new coding territory!
> > _______________________________________________
> > Openvpn-users mailing list
> > Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/openvpn-users
> >
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users