From owner-freebsd-hackers Wed Sep 1 9:42:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.aye.net (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (Postfix) with SMTP id 4A9A6154E2 for ; Wed, 1 Sep 1999 09:42:31 -0700 (PDT) (envelope-from barrett@phoenix.aye.net) Received: (qmail 4459 invoked by uid 1000); 1 Sep 1999 16:32:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Sep 1999 16:32:34 -0000 Date: Wed, 1 Sep 1999 12:32:34 -0400 (EDT) From: Barrett Richardson To: Mark Tinguely Cc: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: IP address caching bug? In-Reply-To: <199909011328.IAA32664@plains.NoDak.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Sep 1999, Mark Tinguely wrote: > > > It seems that an interface configured with an address, which is then > > deleted, and then set to a different address on the same network, the > > machine continues to use the original address although all evidence of it > > is gone. > > delete any static routes before adding a new address: > > # route flush > > most of the time these routes were automatically learned with normal net use. > FreeBSD has behaved like this for a long time. > > --mark. > While we're on the subject, I have a simalar problem. I have some FreeBSD servers that have a FreeBSD box as their default gateway. There is a Cisco routing device on the same segment. Packets from the servers to hosts behind the the Cisco go to the default gateway (this design is an interim design) as expected. The FreeBSD router sends a redirect to the server as expected. The server installs the route in the routing table as expected. But the server still sends packets destined to the host (behind the Cisco) to it's default gateway. I checked the arp tables when this occurs, and noticed that there is no arp entry for the Cisco. If I ping the Cisco to establish an arp entry, the problem goes away and packets are correctly sent to the Cisco. I also noticed the problem occurs when running a routing protocol such as OSPF or RIP that uses multicast. I've had to setup a cron job that periodically pings the Cisco to work around it. Any thoughts? - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message