Sahil,
I''m assuming your network looks like this (appologies for bad ascii
graphics):
10.0.0.0/24 210.54.149.160/27
NET---[cisco]---------------[linux box]-----LAN/DMZ
Is that correct?
If so, your cisco needs to route 210.54.149.160/27 via 10.0.0.2 (eth0 on the
linux box), and your Linux box needs a default route via 10.0.0.1 so traffic
goes out via the cisco (if that is your default route!)
And that''s it. There is no reason to add a route to the
210.54.149.160/27
range on the Linux box because it is directly connected to eth1.
> -----Original Message-----
> From: Sahil Gupta - NET4U [mailto:sahil@sahil.net.nz]
> Sent: Tuesday, January 15, 2002 12:39 PM
> To: lartc@mailman.ds9a.nl
> Subject: [LARTC] Am I on the right Track?
>
>
> Hi there,
> Is it possible to somehow have a fairly basic routing level
> in order to forward packets from eth1 to eth0? Simply using
"route"?
>
> I have a Cisco that has a local network IP. It is on eth0
> interface. I have a Switch on eth1. I want to supply eth1
> with a Real World IP which comes through the Cisco.
>
> Any guidance available?
>
> I assigned 10.0.0.2 on eth0 and 210.54.149.189 on eth1.
> then I did this:
> route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.0.0.1 dev
> eth0 route add -net 210.54.149.160 netmask 255.255.255.224 gw
> 10.0.0.1 (which says network unreachable)
>
> Could someone please tell me how I could solve this?
>
> Regards,
>
> Sahil Gupta
> NET4U Limited
>
> ------------------------------------
> NET4U -- www.net4u.co.nz
> Home of the new - $24.95 128k ADSL
> Nationwide Internet Service Provider
> ------------------------------------
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc > HOWTO:
> http://ds9a.nl/lartc/
>