netdev - Re: Why linux keeps connected routes when link goes down

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: <20090220.121508.252047266.davem@davemloft.net>
Date:	Fri, 20 Feb 2009 12:15:08 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	lsorense@...lub.uwaterloo.ca
Cc:	homecreate@...t.ru, netdev@...r.kernel.org
Subject: Re: Why linux keeps connected routes when link goes down

From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Date: Fri, 20 Feb 2009 12:19:12 -0500

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

This is not necessarily true.

The subnet might be reachable by one of the other interfaces.
Just the same as someone might be able to reach the down
interface's IP address via another one of our interfaces.

The route is tied to the IP address, and the route is therefore
created and destroyed alongside the IP address.

As long as the IP address is active and associated with the
system, so is the route.
--
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