Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!gds
From: gds@sri-spam.istc.sri.com (The lost Bostonian)
Newsgroups: comp.dcom.lans
Subject: Re: routing table management (routed0
Message-ID: <9765@sri-spam.istc.sri.com>
Date: Sat, 6-Dec-86 16:09:47 EST
Article-I.D.: sri-spam.9765
Posted: Sat Dec  6 16:09:47 1986
Date-Received: Sun, 7-Dec-86 03:45:20 EST
References: <675@arthur.cs.purdue.edu> <7541@topaz.RUTGERS.EDU>
Distribution: na
Organization: the Bay Area, for now
Lines: 17

Regarding load sharing, the BBN TCP/IP does load sharing among multiple
routes to a destination net or host.  This can cause problems if the
gateways do not agree that the path of least resistance should be taken.
The host does not listen to redirects until the load is sufficiently
high on the old path of least resistance.  (Some people on the tcp-ip
list are suggesting that loading factors should be figured into internet
gateway routing mechanisms, which is probably a good idea).

Regarding changing the gateway to destinations in routing tables, it
seems like a relatively easy thing to do (in the code in
/sys/net/route.c, once you have hashed on the destination, you could
replace the gateway with the new gateway).  Why this hasn't been done is
a good question (maybe someone at berkeley will answer it).  Some
route-specific information would need to be changed, such as the refcnt
and flags.

--gregbo