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

Re: [Openvpn-users] Another routing issue


  • Subject: Re: [Openvpn-users] Another routing issue
  • From: Zvone Zagar <zvone.zagar@xxxxxxxx>
  • Date: Tue, 14 Dec 2004 00:36:32 +0100

Steve Kieu wrote:

Try

route add -net 172.16.101.0 netmask 255.255.255.0



Why sunny has 172.16.0.0 through eth0 whereas ifconfig
eth0 shows the ip addr of eth0 is 172.16.101.8 ?


Sadly, but I don't quite understand. Sunny and OpenVPN gateway are on the same 172.16.0.0/255.255.0.0 LAN (Sunny has 172.16.101.8, gateway has 172.16.101.11; both have mask 255.255.0.0 and broadcast 172.16.255.255 - Sunny can reach gateway and vice verse)

let's make it clear, from your lengthy emaul :-) here
is what I summarize:

Office vpn gateway

eth0 172.16.101.11
eth1 192.168.1.100
ppp0 *
tun0 10.10.10.10 => 10.10.10.100



Correct

Route is:

192.168.10.0 gw 10.10.10.100 (so there is a route to
your home lan)

172.16.0.0 via eth0 (not get it? where is network
172.16.0.0? can not find it anywhere)



The output of 'route' on office gateway shows 172.16.0.0 LAN. I checked my post.

it should be 172.16.101.0 via eth0

Now the home vpn
eth0 192.168.10.10
eth1 192.168.1.99
ppp0 *
tun0 10.10.10.100 => 10.10.10.10 route:
172.16.0.0 gw 10.10.10.10




Correct

sunny:
eth0 172.16.101.8
route:
192.168.10.0 gw 172.16.101.11 (rout to home lan
through office vpn this route is fine)
172.16.0.0 via eth0.



Correct

OK suppose the info I got is correct we trace the fate
of packet from home to sunny:

ping 172.16.101.8

Home does not know how to route no 172.16.101.0 in its
routing table. Then you add route add -net 172.16.101.0 netmask 255.255.255.0 gw
10.10.10.10


Home gateway has been set: route add -net 172.16.0.0 netmask 255.255.0.0 gw 10.10.10.10. Office server and gateway live in that network.

Now home knows ; and it will send the packets t0
10.10.10.10 through tun0, reach the office.
Now the office in turn it doesn't understand
172.16.101.0 network. It has only the route to
172.16.0.0 ; not 172.16.101.0 even it has the IP
172.16.101.11
If you fix that problem the Office would be able to
know where to send ; (which is eth0) and it will
finally reach sunny box. The route back is fine.

So you should examine why the Office and sunny has
strange network like that. Is it unintentional or
intentional? If not try to re configure those boxes
and fix it. so that u have



I hope I have answered in the first paragraph.

office: eth0 172.16.101.11 there will be no route 172.16.0.0 ; instead it would
be
172.16.101.0 via eth0


The same for sunny; there will not be the route
172.16.0.0 but 172.16.101.0 via eth0.

For quick test try at office
route add -net 172.16.101.0 netmask 255.255.255.0 dev
eth0

and at sunny
route add -net 172.16.101.0 netmask 255.255.255.0 dev
eth0

and test again..





I did as You suggested. But the result is always the same. You have spent to much precious time to solve my problem.
I am going to dig deeper and will let you know when the 'beast' will be reached (I hope in my lifetime).




=====
S.KIEU

Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com



Thanks  Zvone Z.

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