netdev - Re: [PATCH 1/2] IPV4: remove addresses and routes when carrier is lost

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 6 Jun 2008 10:56:05 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] IPV4: remove addresses and routes when carrier is lost

On Mon, Jun 02, 2008 at 04:52:49PM -0700, Stephen Hemminger wrote:
> This patch adds a new configuration sysctl that causes link loss to clear
> FIB state in the same way as admin down. This allows for routing daemons
> like Quagga which have option to remove routes when carrier is lost.
> 
> This has been a long standing problem with Quagga on Linux with complaints
> on the developers list going back to 2004. Fixing it properly, so the routing 
> daemon manages the RIB, and the kernel manages the FIB, requires changes to
> both parts.

There is one slight annoyance in the behaviour of this patch.

It only takes effect the first time link is lost, so if you boot with a
port without link, its addresses and routes are still added, and only
after it gains link and looses it again does it get removed.  Makes for
a somewhat inconsistent behaviour unfortunately.

Any idea how to change that?

Otherwise this looks like a very useful patch when combined with zebra
to manage static routes with link-detect (along with vyatta's updates to
zebra to make it actually obey link detect for routes).

-- 
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