netdev - ipv4 dead route delete notification on netdev 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-next>] [day] [month] [year] [list]

Message-ID: <541E4DD4.1050609@cumulusnetworks.com>
Date:	Sat, 20 Sep 2014 21:02:28 -0700
From:	Roopa Prabhu <roopa@...ulusnetworks.com>
To:	netdev <netdev@...r.kernel.org>
CC:	David Miller <davem@...emloft.net>,
	Stephen Hemminger <stephen@...workplumber.org>,
	nicolas.dichtel@...nd.com, Thomas Graf <tgraf@...g.ch>
Subject: ipv4 dead route delete notification on netdev down

Hi,

The kernel does not send notification for deleted dead ipv4 routes on 
netdev down.
This has been brought up before and patches for the fix have been rejected.
The reason for rejection is that the routing daemons are expected to 
purge their
routing tables on netdev down notifications.

http://www.spinics.net/lists/netdev/msg215161.html
http://lists.openwall.net/netdev/2013/10/17/55

This issue keeps coming back. We run into this too. Wanted to send this 
email out to see if opinions have changed.

There are multiple problems:
1) inconsistency in kernel notification behavior between ipv4 and ipv6 
for dead routes
2) Its not just the routing daemons, its also the userspace netlink 
caches like libnl. In abcense of a direct notification,
these will have to purge the routes on link down too.

Thanks,
Roopa

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