lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 20 Feb 2009 12:19:12 -0500 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: David Miller <davem@...emloft.net> Cc: homecreate@...t.ru, netdev@...r.kernel.org Subject: Re: Why linux keeps connected routes when link goes down On Wed, Feb 18, 2009 at 03:52:07PM -0800, David Miller wrote: > Because the IP addresses are still assigned to the interface. > > IP addresses are owned by the "host" rather than specific interfaces > under Linux. So just bringing an interface down does not disable > IP addresses configured to that interface. > > If you want all the routes to go away, explicitly delete the IP > addresses. An interface IP address and the router to the connected subnet are not the same thing. Keep the IP address but drop the route to the subnet you can no longer reach. By elliminating the route to stuff you can no longer reach, quagga can do its job to provide an alternative way to reach the subnet. It can not do so as long as the kernel insist on providing a now useless route. -- Len Sorensen -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists