netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@6wind.com
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: Fri, 07 Sep 2012 14:18:08 -0400 (EDT)	[thread overview]
Message-ID: <20120907.141808.933339383624986735.davem@davemloft.net> (raw)
In-Reply-To: <1346946815-3094-1-git-send-email-nicolas.dichtel@6wind.com>

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? :-)

  parent reply	other threads:[~2012-09-07 18:18 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 [this message]
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=20120907.141808.933339383624986735.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=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;
as well as URLs for NNTP newsgroup(s).