Re: routing problem

["Doug MacFarlane" <madmac@covad.net>]

On 04 Oct 2002, 19:35:14, Kourosh wrote:
> On Fri, Oct 04, 2002 at 08:24:51PM -0600, dave mallery wrote:
> Have you enabled IP forwarding on buster?  Do you have firewalling enabled
> on buster?

The answer is that you need to configure Buster to function as a router.
 Just configuring Buster to be a part of both networks does NOT mean that
Buster will automagically send packets originating on one network to the
other network.

There are several ways to accomplish this.  You can enable IP Forwarding,
as suggested, or you can run routed, an IP routing daemon.

Since you only need to forward/route the one segment, IP Forwarding will
be much more straight-forward, although every host on your 10.42.42 subnet
will need a static route to buster for the 10.42.43 subnet, otherwise, they
will send everything to the firewall, and the firewall will put it back on
the 10.42.42 subnet addressed to buster (provided you have that rule configured
on the firewall).

madmac



> 
> > (i realize that i will have to add a route to the firewall to the cluster
> > but that can wait till c0n1 can ping bilbo!)
> 
> The cluster doesn't need a route to the firewall, it only needs a default
> route to buster and buster can forward connections to the firewall.
> 
> > is this a routing problem, or am i looking endlessly in the wrong place?
> > i am at a dead stop.  i would so appreciate some pointers.
> > 
> > thanks in advance.
> > 
> > dave
> 
> Hope this helps.
> 
> Kourosh
> 
> 


-- 
Doug MacFarlane
madmac@covad.net