Re: iproute problem

[Jody Shumaker <jody.shumaker@xxxxxxxxx>]

Are you sure 172.20.1.1 doesn't block pings? Is there anything else wrong with the setup besides the pings not working? It's not that uncommon for a server to not respond to ping.

- Jody

On 1/12/06, Alexandre <alex.hocquel_NOSPAM_@xxxxxxx> wrote:

Hello,

I'm on Debian Sarge, and try actually to setup iproute this way :
- local network 1: 192.168.12.0/24
- local network 2: 172.20.0.0/16
- one router on both network : 192.168.12.50 & 172.20.201.50
- one router to internet (SLIS) : 172.20.1.1

I want from my 1st local network to access internet...

here are my lines... (taken from The LARTC Howto)

ip route add 172.20.0.0/16 dev ra0 src 172.20.201.50 table Project
ip route add default via 172.20.1.1 table Project
ip route add 172.20.0.0/16 dev ra0 src 172.20.201.50
ip route add default via 172.20.1.1
ip rule add from 172.20.201.50 table Project
ip route add 192.168.12.0/24 dev eth0 table Project
ip route add 127.0.0.0/8 dev lo table Project

after that :

# ip route show
192.168.12.0/24 dev eth0  proto kernel  scope link  src 192.168.12.50
172.20.0.0/16 dev ra0  proto kernel  scope link  src 172.20.201.50
default via 172.20.1.1 dev ra0

and if I try from local network 1:
$ ping 172.20.201.50
it works, I can even access with ssh on
but:
$ ping 172.20.1.1
doesn't work!

what's the problem?

Any suggestion will be appreciated ;-)

thanks by advance,

Alexandre

_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc