From owner-freebsd-hackers  Tue Sep 26 22:15:13 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA13813
          for hackers-outgoing; Tue, 26 Sep 1995 22:15:13 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA13776
          for <hackers@freebsd.org>; Tue, 26 Sep 1995 22:14:08 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id PAA11050; Wed, 27 Sep 1995 15:11:15 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199509270511.PAA11050@asstdc.scgt.oz.au>
Subject: Re: SLIP and DNS problem
To: joerg_wunsch@uriah.heep.sax.de
Date: Wed, 27 Sep 1995 15:11:13 +1000 (EST)
Cc: radova@risc6.unisa.ac.za, hackers@freebsd.org
In-Reply-To: <199509262031.VAA15240@uriah.heep.sax.de> from "J Wunsch" at Sep 26, 95 09:30:59 pm
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 423       
Sender: owner-hackers@freebsd.org
Precedence: bulk

> It rather looks like the infamous "stale clone route" problem.

 [ .. ]

> The only known workaround by now is to delete any potential host route
> to the intented new host address right before configuring the SLIP
> interface.  It works for sax.sax.de now this way (yes, i've been
> complaining about this problem before).

 .. or to run gated which periodically scans the interfaces and deletes
bogus routes,

	michael