SUMMARY (conclusion): Routing problem

Date: Fri May 28 1993 - 05:33:02 CDT

To start with, here's the partial summary posted the other day.

> >I say 'netstat -r', and I see this:
> >
> > ---------------------
> > zinc# netstat -r
> > Routing tables
> > Destination Gateway Flags Refcnt Use Interface
> > localhost localhost UH 9 23390 lo0
> > blazer zinc UH 0 0 du0
> > default blazer UG 1 963 du0
> > zinc U 34 268792 le0
> > zinc U 1 389 le0
> > ---------------------
> >
> >The last line, where network .64 points to zinc, is wrong, and should
> >be removed. (It shows up automatically, I don't know why.)
> EXTRA CREDIT (unresolved):
> --------------------------
> It's still not clear why the .64 route showed up in the first place.
> Many respondents asked to see the 'ifconfig' readout: here it is.
> inet netmask ffffffe0 broadcast
> Also, here is the /etc/netmasks file:
> < wrong route to this net
> < zinc lives here
> Someone at Sun recently told me that this is an 'illegal'
> netmasks file, because there was more than one line.

In hindsight I should have mentioned that the router involved
here is a Telebit NetBlazer, not a 'typical' router used on
Sun networks. In particular, the NetBlazer has different rules
about netmasks, as I will detail below.

It turns out that the extra route, to network .64 is *not* incorrect.
It's probably a route RIP'ed to zinc by the Blazer. Normally, I would
expect that route to .64 should have a gateway of 'blazer' (the router),
but I have been told that, with a Blazer, a route through gateway 'zinc'
is OK. In other words, it appears that nothing is wrong.

Some respondents have told me that the above /etc/netmasks file
is indeed illegal, and that it should have only one line, which
gives the one-and-only netmask for our Class C subnet.

Yes, Suns-when-used-as-routers and 'typical' Sun routers (e.g. Cisco)
only know how to deal with one netmask per subnet. Such a router
simply scans the entry to see if it's Class A/B/C, and then assigns
the netmask to that network.

But, we are using a Telebit NetBlazer as a router, which can handle
much more general netmasks. In particular, it is possible for the
Blazer to handle several different netmasks for the same subnet,
which is what we are doing. Now, the Blazer evidently does not
consult /etc/netmasks, so our /etc/netmasks has no real function
except for reference.

to the following good souls for their help:

Tobias Weingartner
Geordie F. Klueber
Barry Margolin
Casper Dik
Tom Crummey
David Comay
Christian Lawrence
Russ Poffenberger
Dan Jiracek
Rod Livingood
Mike Raffety
Jerry Springer
Matt Mauss
Paul Lord
Geert Jan de Groot

David Mostardi Email:
Senior Support & Systems Manager Phone: (510) 540-6400
Capital Market Technology, Inc. FAX: (510) 540-5505
1995 University Ave. #390, Berkeley CA 94704

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:53 CDT