routes are killing me - how to?

[Bil]

ok, i didn't say check the IP was assigned, i meant to actually ping the IP
from the box, just to make sure the NIC isn't acting funny, and to see if
you could pick up maybe a firewall problem.

Bill Finks gives some hints, but atm, it's not a routing problem, nor a NAT
problem, back down to networking. Check everything and double check it,
something between them is causing a problem, be it dodgy switch or firewall
or misconfiguration.

if you get any leads. i'll be following the thread.

bil
----- Original Message -----
From: "Stefan Jeglinski" <jeglin@4pi.com>
To: <yellowdog-general@lists.terrasoftsolutions.com>
Sent: Friday, November 08, 2002 1:57 AM
Subject: Re: Re: routes are killing me - how to?


> >get the linux box to ping 127.0.0.1
> >then ping 192.168.0.1
>
> Yep, as the IP 192.168.0.1 is assigned to the NIC in the Linux box.
>
>
> >get the osx box to ping 127.0.0.1
> >and then 192.168.0.222
>
> Yep, as the IP 192.168.0.222 is assigned to the NIC in the OSX box.
>
> That all works.
>
>
> >the routing table won't matter if a cable is cross over when it's meant
to
> >be patch. be sure to check that.
>
> That's been checked. More than once.
>
>
> >i'm thinking maybe there's some residual firewall config. if not then i
hope
> >it's that cable issue. otherwise this could get to be serious difficult
to
> >help with.
>
> Do you have a comment on my earlier question? That is, if there are 2
> NICs in a box, each assigned to a different subnet, and one pings an
> outside network, what decides which interface the pings go out on?
> It's not random is it? I've always been curious about this question
> no matter what my other problems.
>
>
> Stefan Jeglinski
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>
>