All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naohiro Ooiwa <nooiwa@miraclelinux.com>
To: Fey Marcus <Fey@iabg.de>
Cc: usagi-users@ml.linux-ipv6.org,
	"YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>,
	netdev@vger.kernel.org, usagi-users@linux-ipv6.org
Subject: Re: (usagi-users 04056) Re: ping6 is sent out from wrong interface
Date: Thu, 26 Jun 2008 09:48:26 +0900	[thread overview]
Message-ID: <4862E75A.8060006@miraclelinux.com> (raw)
In-Reply-To: <69A5E767EC979846826F566C7932A3F207233D99@exchange03.iabg.de>

Hi Marcus

Thank you for your comment.

>>
>> Thank you for your quick reply.
>>
>>> It's due to routing.
>> For the reason of selecting 'eth0', I agree.
>> But, I think the device is specified before looking up the 
>> routing table in this case.
> 
> Well, ping's man page reads: 
> ---
>        -I interface address
>               Set source address to specified interface  address.  Argument
>               may  be  numeric  IP  address or name of device. When pinging
>               IPv6 link-local address this option is required.
> ---
> 
> So you only set the address, not the interface to be used for sending.

Then, the man page doesn't match with the implementation.

> 
>>> ...with eth0 being preferred over eth1 for multicast packets.
>>> You could add a dedicated route for ff02::/16 to make the 
>> kernel output the packet via eth1.
>>
>> This works when using only "eth1" for multicasts.
>> When multiple I/Fs are connected to separate networks, this 
>> scheme requires changing the route every time a user need to 
>> send ping to different network.
>>
> 
> Ok, my proposition was a bit too general. It would probably be better to set up routes for the exact addresses. So in your case to ff02::1. 
> 
> Of course, if you wish to send the same packet via several interfaces within a short time, this would still result in adding and deleting the routes over and over again.
> 
>> I think kernel can solve this problem better.
>>
> 
> I don't think this would be intended....
> 

I was just confused by the difference of
source address things between IPv4 and IPv6.

Regards,
Naohiro Ooiwa



  reply	other threads:[~2008-06-26  0:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  7:02 ping6 is sent out from wrong interface Naohiro Ooiwa
2008-06-25  7:51 ` (usagi-users 04057) " Fey Marcus
2008-06-25 10:18   ` (usagi-users 04056) " Naohiro Ooiwa
2008-06-25 11:26     ` Fey Marcus
2008-06-26  0:48       ` Naohiro Ooiwa [this message]
2008-06-27 19:14 ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-30 12:57   ` Naohiro Ooiwa

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=4862E75A.8060006@miraclelinux.com \
    --to=nooiwa@miraclelinux.com \
    --cc=Fey@iabg.de \
    --cc=netdev@vger.kernel.org \
    --cc=usagi-users@linux-ipv6.org \
    --cc=usagi-users@ml.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 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.