From fortin@zap.zap.qc.ca  Sat Jan 21 14:54:28 1995
Received: from zap.zap.qc.ca (zap.qc.ca [192.219.247.8]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id OAA21715 for <FreeBSD-gnats-submit@freebsd.org>; Sat, 21 Jan 1995 14:54:19 -0800
Received: (from fortin@localhost) by zap.zap.qc.ca (8.6.9/8.6.6) id RAA09764; Sat, 21 Jan 1995 17:47:10 -0500
Message-Id: <199501212247.RAA09764@zap.zap.qc.ca>
Date: Sat, 21 Jan 1995 17:47:10 -0500
From: fortin@acm.org
Reply-To: fortin@acm.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: Weird route problem with the 2.0-950112-SNAP version
X-Send-Pr-Version: 3.2

>Number:         162
>Category:       misc
>Synopsis:       routes seem to accumulate under 2.0-950112-SNAP
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    wollman
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jan 21 15:00:01 1995
>Closed-Date:    Sun Oct 29 11:10:48 PST 1995
>Last-Modified:  Sun Oct 29 11:11:38 PST 1995
>Originator:     Denis Fortin
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
DMR Group Inc
>Environment:
		Recently installed 2.0-950112-SNAP on a 386; recompiled
		gated under the new version of the O/S.
>Description:
		Upgraded to the latest snapshot last night.  After 12 hours
		of operation, the list of routes on our gateway has grown
		to contain a ton and a half of lines (I was going to include 
		the output of "netstat -rn", but the machine has just crashed)!

		Has something major changed in the handling of routes?  (I used
		the same configuration file for gated that I used to build it
		under 2.0)

>How-To-Repeat:
		Let the system run for a while; type "netstat -r".  Notice
		how long the list of machines is; worry that the non-removal
		of old routes may be what causing login problems for folks
		running SLIP.

>Fix:
		I've just encountered this; I haven't had the time to 
		search for a fix.  I might try to revert to good old (?)
		routed, and see if that helps, but I'm not convinced
		(cf: bmk@dtr.com's problems with routed).

		Any suggestions?
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: wollman 
State-Changed-When: Sat Jan 21 15:34:12 PST 1995 
State-Changed-Why:  
The accumulation of routes is not a bug, but I'm working on a fix for 
the problem of toutes changing out from under their children. 


Responsible-Changed-From-To: freebsd-bugs->wollman 
Responsible-Changed-By: wollman 
Responsible-Changed-When: Sat Jan 21 15:34:12 PST 1995 
Responsible-Changed-Why:  
I'm working on it. 
State-Changed-From-To: analyzed->closed 
State-Changed-By: wollman 
State-Changed-When: Sun Oct 29 11:10:48 PST 1995 
State-Changed-Why:  
This problem was fixed by changes committed in the spring of this year. 
>Unformatted:


