From owner-freebsd-net Mon Jun 28 9:12:29 1999 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5D91E1530C for ; Mon, 28 Jun 1999 09:12:22 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA17098; Mon, 28 Jun 1999 12:12:10 -0400 (EDT) (envelope-from wollman) Date: Mon, 28 Jun 1999 12:12:10 -0400 (EDT) From: Garrett Wollman Message-Id: <199906281612.MAA17098@khavrinen.lcs.mit.edu> To: Kevin Bracey Cc: freebsd-net@freebsd.org Subject: Old IP addresses hanging around in routes In-Reply-To: <5210331949%kbracey@kbracey.acorn.co.uk> References: <5210331949%kbracey@kbracey.acorn.co.uk> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Our particular problem is that if you change the IP address of an interface, > you end up with severe communication difficulties. The reason for this is > that the routing table is full of references to struct ifaddrs containing > our previous IP address - in particular the cloned link-level routes, our > default route and any protocol-cloned TCP routes. There is supposed to be code in there to delete all of the (non-static) routes which refer to a specific interface when that interface goes down. At least, I feel fairly certain that I wrote code to do that; I can't seem to find it right now. I think in_ifscrub ought to be doing it, but I don't see the code that would, either there or in rtinit. The cloned-route cleanup in rtrequest(RTM_DELETE,...) ought to take care of it too. You are correct that 4.4BSD did not have any such code. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message