From owner-freebsd-hackers  Thu Apr 11 19:35:09 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id TAA10086
          for hackers-outgoing; Thu, 11 Apr 1996 19:35:09 -0700 (PDT)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA10076
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 11 Apr 1996 19:35:01 -0700 (PDT)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.5/BSD4.4) id MAA20656
          Fri, 12 Apr 1996 12:34:27 +1000 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199604120234.MAA20656@asstdc.scgt.oz.au>
Subject: Re: PPP routing problem
To: joerg_wunsch@uriah.heep.sax.de
Date: Fri, 12 Apr 1996 12:34:25 +1000 (EST)
Cc: freebsd-hackers@FreeBSD.ORG, scrappy@ki.net
In-Reply-To: <199604112209.AAA06535@uriah.heep.sax.de> from "J Wunsch" at Apr 12, 96 00:09:02 am
X-Mailer: ELM [version 2.4 PL24beta]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

J Wunsch writes:

> The only workaround i've found for it by now (short of understanding
> the routing code in the kernel) was to run ``arp -d'' for this IP
> address in the ip-up script, and retrying the ifconfig.  This still
> leaves a minor window where a new incoming packet for this IP address
> could trigger another ARP attempt.

You could run gated, which seems to keep track of the links that are up (or
down) correctly and tells the kernel,

	michael