All,

Yes, as I suggested, I have figured out my problem and it was indeed something
I want to slap myself over.  I neglected to recall a basic concept and even
though some of you pointed out my error, I kept misreading what you stated.

My problem was not that I misconfigured the new Linux router or the hosts on
the 192.168.0.0 network.  It was that I neglected to add a route to the hosts
on the 10.1.1.0 network back to the 192.168.0.0 network.  Once I did so, I
became able to ping the 10.1.1.0 hosts from 192.168.0.0 machines.  Somehow I
forgot that it needs to be a two-way street.  Ugh.

I apologize for taking everyone's time.  I learned new things in the process
though.

-Ian



Ian Zapczynski wrote:

> Thanks again, all, for your thoughts and suggestions.
>
> You're right - the static routes were overkill.  I have since removed them,
> but for some reason I am still unable to route between the two networks.
>
> Indeed I have set my router as the default gateway for my client machines
> using the 192.168.1.1 address that they can contact it on.  When a client
> machine tries to ping a 10.1.1.0 address, I can see via Ethereal that the
> request goes to my router.  I just still stumped as to why it won't forward
> the traffic on to the proper host!
>
> Being somewhat green on Linux administration, I even went to the bookstore
> last night to check out a Red Hat admin book.  It seems to tell me pretty
> much what you kind folks have already told me.
>
> Hmmm... when I figure this out, I know it's going to be something I'll want
> to slap myself over.  ;-)