From: David Miller <davem@davemloft.net>
To: remi@remlab.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sit: 6to4: honour routing table
Date: Fri, 28 Aug 2009 23:55:32 -0700 (PDT) [thread overview]
Message-ID: <20090828.235532.253821244.davem@davemloft.net> (raw)
In-Reply-To: <f40a9bc1410c815bf1932e27086162d8@chewa.net>
From: Rémi Denis-Courmont <remi@remlab.net>
Date: Mon, 24 Aug 2009 12:02:51 +0200
>
>
> On Mon, 24 Aug 2009 11:48:12 +0200, Sascha Hlusiak
> <contact@saschahlusiak.de> wrote:
>> Attached patch is a compromise though which implements both but tries the
>
>> destination address first and then the next hop. What would it break?
>
> I don't think it breaks anything per se. But userland will continue to use
> compatible addresses forever anyway, so that it works with current kernel
> versions.
This is reason enough for me to not apply this patch.
prev parent reply other threads:[~2009-08-29 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 10:47 [PATCH] sit: 6to4: honour routing table Sascha Hlusiak
2009-08-24 2:05 ` David Miller
2009-08-24 6:37 ` Rémi Denis-Courmont
[not found] ` <200908241148.17012.contact@saschahlusiak.de>
[not found] ` <f40a9bc1410c815bf1932e27086162d8@chewa.net>
2009-08-29 6:55 ` David Miller [this message]
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=20090828.235532.253821244.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=remi@remlab.net \
/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