[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Linux and Routing
okay, that routing table is correct as far as the linux box is concerned,
but what about...
the routing table of the machine on the inside (eth1) network that can't
get out. What is its default gateway?
the machines on the (eth0) network... are they configured for the cisco as
their default gateway? If so, does it know about the .40 network? What
does the routing table on one of these machines look like
----------
> From: KoReE <koree@ameth.org>
> To: SILUG <silug-discuss@silug.org>
> Subject: Re: Linux and Routing
> Date: Wednesday, April 05, 2000 9:00 PM
>
>
> Ugh. Okay, that /42 below was supposed to a 24. Anyway, here's what I
> have so far:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
Iface
> 206.152.121.102 * 255.255.255.255 UH 0 0 0
eth0
> 208.169.40.0 * 255.255.255.240 U 0 0 0
eth1
> 206.152.121.0 * 255.255.255.0 U 0 0 0
eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 0
lo
> default mtv-cs3640-1.mv 0.0.0.0 UG 0 0 0
eth0
>
>
> That's my routing table. I've routed 208.169.40.0/28 to eth1 (or so I
> think). I've assigned eth1 the address 208.169.40.1. I have also
plugged
> an ethernet hub to eth1. Into that hub, I've plugged in a machine that
> has been given the address 208.169.40.2. With the above routing table, I
> can traceroute from outside our network to 208.169.40.1, and I can ping
> it. I can also ping 208.169.40.2 from the Linux box that I'm routing
> with, and the 208.169.40.2 box can communicate with the Linux box, but, I
> can't trace to it, nor can it ping the outside world. So, I know that
the
> Linux box is not gatewaying the 208.169.40.0/28 network for some reason,
> but I can't figure out why. I've tried adding all sorts of routes, and
> none seem to work. Any ideas anyone?
>
> Thanks,
>
> Koree
>
--
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.