Re: Woody routing question...
Sean Cardus, 2002-Aug-09 09:40 +0100:
>
> On to the problem... Machines with eth0's local subnet can communicate
> with the server without a problem. Machines outside of the subnet - eg.
> aaa.bbb.81.36 - cannot communicate with this interface's ip address.
> aaa.bbb.81.36, as well as external Internet hosts, can however connect to
> xxx.yy.234.131 without a problem.
>
I did some drawing based on your explanation and came up with this:
a.b.80.0/21---[ ? ]---[eth0--eth1]---{Internet}
The [ ? ] has to be a router since there are other subnets on this
side of you server. As I see it, this is your problem. I believe
this mystery box has it's own route to the Internet which is providing
a path to eth1. You can solve this 2 ways at this point:
1. Remove the default route pointing to eth1 so that all
non-connected routes go to the mystery box, which will provide
valid paths.
- However, this will push all traffic to eth1 out over the
Internet, which may not be desired.
2. Find the mystery box and it's admin and fix the routing there. It
simply need 1 additional route pointing to eth0 to access eth1.
I hope this helps...jc
--
Jeff Coppock Systems Engineer
Diggin' Debian Admin and User
Reply to: