Date: Mon, 28 Jun 1999 11:18:15 +0100 From: Kevin Bracey <kbracey@e-14.com> To: freebsd-net@freebsd.org Subject: Old IP addresses hanging around in routes Message-ID: <5210331949%kbracey@kbracey.acorn.co.uk>
next in thread | raw e-mail | index | archive | help
Our systems use a FreeBSD-derived networking stack, which has served us well for many years. However, during testing of some new DHCP client code, I appear to have opened up a can of worms with regard to interface IP addresses referenced in routing table entries. 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. This is not a FreeBSD-specific problem - it affects all 4.4BSD derivatives, but I'm posting here in the hope that I can find someone knowledgable enough to help work through a solution - comp.protocols.tcp-ip et al are no use whatsoever :) Note that a specific instance of this problem has been reported as kern/2991. -- Kevin Bracey, Senior Software Engineer Pace Micro Technology plc Tel: +44 (0) 1223 725228 645 Newmarket Road Fax: +44 (0) 1223 725328 Cambridge, CB5 8PB, United Kingdom WWW: http://www.acorn.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5210331949%kbracey>