*BSD News Article 76766


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!news.mathworks.com!newsfeed.internetmci.com!in3.uu.net!deathstar.kersur.net!news
From: Chip Ach <chip@harvard.net>
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Routing issue with SDL N2 card
Date: Fri, 23 Aug 1996 10:50:21 -0400
Organization: HarvardNet
Lines: 34
Message-ID: <321DC52D.BF8@harvard.net>
Reply-To: chip@harvard.net
NNTP-Posting-Host: vasthi.chip.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0b6 (Win95; I)

(originally sent to bsdi-users@bsdi.com with no response...Perhaps
someone here?  cc:s appreciated.)

I think this may be a bsdi-specific issue because it SHOULD, as far as
I can tell work...

I have an (well, 3) SDL N2 cards in a machine.  For those of you who
don't know, the N2 cards make the unix box into a router for T1's; you
can connect a T1 onto the card.  The machine's ip is 206.137.218.14.
I have several perfectly happy T1's connected and routing to
206.137.X.2.  X is 93, 95, and 220.  (We have multiple blocks of 8 C
blocks within 206.137...)  These are routed with lines like:

route add -net 206.137.220.0 206.137.220.1

where 220.1 is the router on the other side.  Works like a charm.


What ISN'T working is:

route add -net 208.195.108.0 208.195.108.1

Now, I CAN get to 208.195.108.1 from the machine.  I can get to it
from outside the 206.137.218.X subnet.  I CAN'T get to it from that
subnet, however.  (This is the subnet that the machine itself is on.)

This isn't a problem with the router we have because machines in the
218 subnet know to go to 206.137.218.14 when trying to get to the
208.195.108 subnet.  For some reason the machine with the N2 card
won't route anything on its own subnet to a very different subnet.

Ideas?

-Chip