netdev - IPv6 routing type - not at par with IPv4 one?

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: <loom.20120906T115737-277@post.gmane.org>
Date:	Thu, 6 Sep 2012 10:02:47 +0000 (UTC)
From:	Markus Stenberg <markus.stenberg@....fi>
To:	netdev@...r.kernel.org
Subject: IPv6 routing type - not at par with IPv4 one?

~ # ip route add throw 1.2.3.4
~ # ip -6 route add throw ::1.2.3.4
RTNETLINK answers: No such device
~ # ip route add blackhole 1.2.3.5
~ # ip -6 route add blackhole ::1.2.3.5
RTNETLINK answers: No such device
~ #

The reason for this is in net/ipv6/route.c - ipv6_route_add:

Eventually code winds up at this (1423 line in 3.5.3):

	err = -ENODEV;
	if (!dev)
		goto out;

and poof, ENODEV.

Is there some reason for this? Or should I write a patch? 
Or does someone else want to? Support for dev=NULL 
elsewhere in the code seems to be ok.

Based on quick googling I'm not the first one to have encountered this.

Cheers,

-Markus

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