Adding the route to my default gateway solved the problem !!! thank
you all for the help !!!

Allan

On 9/18/05, capsel <[EMAIL PROTECTED]> wrote:
> AFAIK:
> packets can not reach destinations in other subnet (except 0.0.0.0)
> than the subnet of your IP. You must have assigned an IP address from
> same subnet as destination host.
> 
> so client can ping all 10.... and two sides of server
> Please check if you can ping other IP from 192.168.0.0 subnet.
> 
> My advice is to "fix" routing tables... or to set up NAT, or set
> everywhere same subnet :)
> 
> 2005/9/18, Oliver Friedrich <[EMAIL PROTECTED]>:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Allan Spagnol Comar wrote:
> >
> > > Hi all, I having some strange problem on my VPN :(
> > >
> > > I had configured openvpn as tunnel server-client; had a tun
> > > interface .....
> > >
> > > I started the open vpn using 10.8.0.0 network and has my private
> > > net at 192.168.0.0 and the open vpn is running at 192.168.0.230
> > >
> > > I started one client; the client sync receive an IP 10.8.0.5 and
> > > the route to 192.168.0.0 network;
> > >
> > > Until now everything looks ok, but here is the strange sinc, I can
> > > ping 10.8.0.1 and I can ping 192.168.0.230 but when I try to ping
> > > 192.168.0.1 it got connection time out ....
> >
> >
> > There is the Problem, the 10.8.0.0 Network is only for the connection,
> > your client is on 192.168.0.0 and your server is on 192.168.0.0 too...
> > so as long as the tunnel exists, your server has two 192.168.0.230,
> > one localy and one on the other side of the tunnel...
> >
> > client and server must not be in same subnet, since then the tunnel
> > can cause IP conflicts.
> >
> > Sorry for my bad english
> >
> > Oliver "Beowulf" Friedrich
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.1 (GNU/Linux)
> >
> > iD8DBQFDLd4ecZpid1GuHxcRArn5AKDGMdtppI8iDI2KLccWnBax5Gc33gCg0Eix
> > Ta4t0uJ1UMWLhyLm/SaX1rM=
> > =CDSa
> > -----END PGP SIGNATURE-----
> >
> > --
> > [email protected] mailing list
> >
> >
> 
> --
> [email protected] mailing list
> 
>

-- 
[email protected] mailing list

Reply via email to