From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, markus.stenberg@iki.fi, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] ipv6: fix handling of throw routes
Date: Mon, 10 Sep 2012 09:15:48 +0200 [thread overview]
Message-ID: <504D93A4.4090706@6wind.com> (raw)
In-Reply-To: <20120907.141808.933339383624986735.davem@davemloft.net>
Le 07/09/2012 20:18, David Miller a écrit :
> From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Date: Thu, 6 Sep 2012 11:53:35 -0400
>
>> It's the same problem that previous fix about blackhole and prohibit routes.
>>
>> When adding a throw route, it was handled like a classic route.
>> Moreover, it was only possible to add this kind of routes by specifying
>> an interface.
>>
>> Before the patch:
>> $ ip route add throw 2001::2/128
>> RTNETLINK answers: No such device
>> $ ip route add throw 2001::2/128 dev eth0
>> $ ip -6 route | grep 2001::2
>> 2001::2 dev eth0 metric 1024
>>
>> After:
>> $ ip route add throw 2001::2/128
>> $ ip -6 route | grep 2001::2
>> throw 2001::2 dev lo metric 1024 error -11
>>
>> Reported-by: Markus Stenberg <markus.stenberg@iki.fi>
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>
> Applied, thanks.
>
> See how easy this was to implement via ->rtm_type? :-)
>
Definitely!
next prev parent reply other threads:[~2012-09-10 7:15 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
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 [this message]
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=504D93A4.4090706@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=markus.stenberg@iki.fi \
--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.