No, I think he was talking about the routing table on the Cisco router itself.
You need to let the Cisco router know how it can reach the 172.17.11.0 network.
You tell it to send packets for 172.17.11.0 to 172.17.10.2 and not it's external
default gateway (Internet).

On a side note, why the Class B private IP addresses? I'm assuming your using
them purely as example and not as actual addresses...

> -----Original Message-----
> From: owner-kclug@marauder.illiana.net
> [mailto:owner-kclug@marauder.illiana.net]On Behalf Of Rusty Brown
> Sent: Wednesday, March 19, 2003 2:45 PM
> To: dt@xr7.org
> Cc: kclug@kclug.org
> Subject: Re: Routing question...
>
>
> Yes. There is a route to each 172.17.10. and 172.17.11. network range
> with eth0 and eth1 as the interface to use. And a default route to use
> 172.17.10.1 as the gateway.
>
>
> --- dt@xr7.org wrote:
> > On Wed, 19 Mar 2003, Rusty Brown wrote:
> > > Here's the "lab" setup. 2 linux boxes connected going thru a Cisco
> > > router to get "outside". One linux box has 2 nics, the other 1. The
> > 2
> > > nic box is routing (/proc/sys/net/ipv4/ip_forward = 1) for the
> > single
> > > nic box.
> > >
> > > Addresses are:
> > > Cisco router 172.17.10.1
> >
> > Do you have a route here pointing to 172.17.11.0/24 via the Linux
> > router?
> > You should have something like:
> > ip route 172.17.11.0 255.255.255.0 172.17.10.2
> >
> > dt
> >
> > --
> > Dean Troyer
> > dt@xr7.org
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
>