netdev - ipv6: throw route behaves like unreachable route (IPv4 works)

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>] [day] [month] [year] [list]

Date:	Fri, 13 Mar 2015 10:23:40 +0100
From:	Steven Barth <cyrus@...nwrt.org>
To:	netdev@...r.kernel.org
Subject: ipv6: throw route behaves like unreachable route (IPv4 works)

Hello everyone,

I have the following minimal set of policy rules and routes.

ip -6 rule add lookup 33333 priority 33333
ip -6 route add throw 2001:db8::1
ip -6 route add 2001:db8::1 via fe80::1 dev wlan0 table 33333
ip route get 2001:db8::1

Now I would expect the call to ip route get (and with that also actual 
routing) to route these packages via
fe80::1 on wlan0 however what route get actually returns is:

throw 2001:db8::1 from :: dev lo  src [...]  metric 1024  error -11

Doing the exact same thing with IPv4 in contrast works as expected.

ip rule add lookup 33333 priority 33333
ip route add throw 1.2.3.4
ip route add 1.2.3.4 via 192.168.0.1 dev wlan0 table 33333
ip route get 1.2.3.4

returns:
1.2.3.4 via 192.168.0.1 dev wlan0  src [...]

It seems to me that the throw route in IPv6 does not actually cause 
further evaluation of policy rules and instead behaves like an 
unreachable route.

Do you have any ideas on how to address this or did I miss anything 
important?

My current kernel is 3.19.1 but older kernels (e.g. 3.14) seem to have 
the same issue.

Thanks,

Steven

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