Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Sep 1997 10:53:18 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Alex Weeks <Alex_Weeks@capitalland.com>
Cc:        "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG>
Subject:   Re: I don't understand static routes afterall
Message-ID:  <19970919105318.48856@lemis.com>
In-Reply-To: <01BCC41C.F85A7F20@cutthroat>; from Alex Weeks on Thu, Sep 18, 1997 at 10:23:54AM -0500
References:  <01BCC41C.F85A7F20@cutthroat>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 18, 1997 at 10:23:54AM -0500, Alex Weeks wrote:
> Well, just about the time I thought I new what I was doing I encountered
> the following.  If anyone feels like explaining what's going on I would be
> interested.
>
> I have three subnets.  I have a FreeBSD machine routing between subnet a
> and subnet b and another FreeBSD machine routing between subnet b and
> subnet c.  The is necessary because the physical setup prevents one machine
> from connecting to all three subnets.  Let's call the machine that sits
> between a and b machine A and the machine that sits between b an c machine
> B.
>
> In order to get subnet a to talk with subnet c I needed to include a static
> route in A.  The static route should say something like "route all traffic
> for subnet c through <hostname> on subnet b" where <hostname> physically
> resides in machine B.
>
> Let me put numbers to it.
> Subnet a is 192.1.1.0
> Subnet b is 192.1.2.0
> Subnet c is 192.1.3.0
>
> I should have been able to accomplish the above with "route add -net
> 192.1.3.0 -interface 192.1.2.1" assuming 192.1.2.1 is the 192.1.2.0
> interface in machine B.
>
> But this didn't work.  What's wierd however is that it did work to enter
> each hostname in invididually!  I litterally typed
> route add 192.1.3.1 192.1.2.1
> route add 192.1.3.2 192.1.2.1
> route add 192.1.3.3 192 1.2.1
> etc....... for the entire subnet.  Now it's working fine.
>
> Have I made a glaring error?  Do I completely misunderstand subnets and
> routing?

It would be nice to see the output of netstat -r and possible netstat
-a.

Greg

> In real life these are 27 bit class c subnets but that shouldn't matter for
> the example.  I did include a "-netmask" statement in real life but it
> wouldn't make sense for this example.

Just possibly it would.  I've seen some bugs in this area when the
tables get big.

Greg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970919105318.48856>