From: Steven Barth <cyrus@openwrt.org>
To: netdev@vger.kernel.org
Subject: ipv6: throw route behaves like unreachable route (IPv4 works)
Date: Fri, 13 Mar 2015 10:23:40 +0100 [thread overview]
Message-ID: <5502AC9C.7070101@openwrt.org> (raw)
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
reply other threads:[~2015-03-13 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5502AC9C.7070101@openwrt.org \
--to=cyrus@openwrt.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.