From: Eric Dumazet <eric.dumazet@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Cc: netdev@vger.kernel.org, Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: IPv6 routing type - not at par with IPv4 one?
Date: Thu, 06 Sep 2012 12:35:05 +0200 [thread overview]
Message-ID: <1346927705.2484.22.camel@edumazet-glaptop> (raw)
In-Reply-To: <loom.20120906T115737-277@post.gmane.org>
On Thu, 2012-09-06 at 10:02 +0000, Markus Stenberg wrote:
> ~ # 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.
Well, it seems you missed this :
http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commitdiff;h=ef2c7d7b59708d54213c7556a82d14de9a7e4475
At least the blackhole is now supported on IPv6, so you probably have to
add the 'throw' bit, if it makes any sense.
next prev parent reply other threads:[~2012-09-06 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 10:02 IPv6 routing type - not at par with IPv4 one? Markus Stenberg
2012-09-06 10:35 ` Eric Dumazet [this message]
2012-09-06 10:54 ` Markus
2012-09-06 13:21 ` Nicolas Dichtel
2012-09-06 15:53 ` [PATCH net-next] ipv6: fix handling of throw routes Nicolas Dichtel
2012-09-06 13:58 ` Eric Dumazet
2012-09-07 18:18 ` David Miller
2012-09-10 7:15 ` Nicolas Dichtel
2013-01-24 10:11 ` Axel Neumann
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=1346927705.2484.22.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=markus.stenberg@iki.fi \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox