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

From: Ханкин Константин <homecreate@...t.ru>
Date: Mon, 23 Feb 2009 23:02:55 +0500

> Linux is used as router in many places, such behavior is a
> suicide. Of course, one can use ifplugd (so do I), but it's a crap
> for network OS, don't you think so?

The default behavior for a general purpose operating system is
to increase the likelyhood of successful communication.

And the way to maximize successful communication is to associate
addresses with the host rather than the interface.

This decision was made at least 10 years ago, and if you think what we
have now is broken just imagine how much struff would explode if we
changed things.