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.153353.237733933.davem@davemloft.net>
Date:	Mon, 23 Feb 2009 15:33:53 -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: Mon, 23 Feb 2009 09:38:30 -0500

> On Fri, Feb 20, 2009 at 12:15:08PM -0800, David Miller wrote:
> > The route is tied to the IP address, and the route is therefore
> > created and destroyed alongside the IP address.
> 
> That's how it works now.  It wasn't how it worked in linux a long
> time ago.  Long ago you had to create the route yourself in userspace
> (which was actually to some extent better than the current setup).
> The current method is simpler to understand for your typical user though.

I don't remember Linux ever not creating a subnet route when an IP
address was added to an interface.  And I also don't remember Linux
ever deleting an IP address on interface down.

Maybe it happened back in 0.99pl5 times, but we're talking at least
10 years ago.
--
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