netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ville Nuorvala <vnuorval@tcs.hut.fi>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, usagi-core@linux-ipv6.org
Subject: Re: [RFC] [GIT PATCH] IPv6 Routing / Ndisc Fixes
Date: Thu, 10 Aug 2006 13:20:32 +0300	[thread overview]
Message-ID: <44DB0870.6000902@tcs.hut.fi> (raw)
In-Reply-To: <20060810.174635.42119608.yoshfuji@linux-ipv6.org>

YOSHIFUJI Hideaki wrote:

> As a result of original lookup (with possible ambiguous outout interface),
> one interface for original output is selected.
> Which means, we have a route for the (original) destination through that
> interface.
> 
> Redirects shall come from that interface.
> So, it is enough to lookup routes on that interface.

Yes, exactly.

Regards,
Ville

  reply	other threads:[~2006-08-10 10:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 10:56 [RFC] [GIT PATCH] IPv6 Routing / Ndisc Fixes YOSHIFUJI Hideaki / 吉藤英明
     [not found] ` <44D9D431.10101@tcs.hut.fi>
2006-08-09 21:37   ` Ville Nuorvala
2006-08-10  8:46     ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-10 10:20       ` Ville Nuorvala [this message]
2006-08-10 12:07         ` Possible leak of multicast source filter sctructure Michal Ruzicka
2006-08-10 12:12           ` David Miller
2006-08-10 12:13             ` David Miller
2006-08-10 18:07           ` David Stevens
2006-08-23 11:08           ` multicast group memberships purge on interface delete Michal Ruzicka
2006-08-23 12:32             ` jamal
2006-08-23 13:29               ` Michal Růžička
2006-08-23 14:48                 ` jamal
2006-08-23 18:51             ` David Stevens
2006-08-24  0:40       ` [RFC] [GIT PATCH] IPv6 Routing / Ndisc Fixes David Miller
     [not found]   ` <44DA274C.30205@tcs.hut.fi>
2006-08-10  0:05     ` David Miller

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=44DB0870.6000902@tcs.hut.fi \
    --to=vnuorval@tcs.hut.fi \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=usagi-core@linux-ipv6.org \
    --cc=yoshfuji@linux-ipv6.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 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).