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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080603085707.51fdabbb@speedy>
Date:	Tue, 3 Jun 2008 08:57:07 -0700
From:	Stephen Hemminger <stephen.hemminger@...tta.com>
To:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Cc:	Stephen Hemminger <shemminger@...tta.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] IPV4: remove addresses and routes when carrier is
 lost

On Tue, 3 Jun 2008 11:05:24 -0400
lsorense@...lub.uwaterloo.ca (Lennart Sorensen) wrote:

> 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.
> 
> Does this cover only the local route for the interface, or all routes
> assigned staticly to the interface too?

The patch makes carrier down == interface down. So the same
behaviour as doing 'ip link set dev eth3 down'

> Certianly if I do ifconfig eth3 down, it removes all the routes, but
> doing ifconfig eth3 up only adds back the directly connected network
> based on the IP and netmask, but my static routes are gone which is a
> problem.

If you are using a routing daemon like quagga, it will restore your static
routes.


> I have been considering writing a user space daemon to listen on netlink
> for link up/down events to remove routes from the routing table and then
> add them back when the link is restored since I couldn't find a good way
> to make the kernel remember the static routes when the link was brought
> down.

That is pretty much what zebra portion of quagga does.
--
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