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: Wed, 25 Jun 2008 19:18:38 +0900	[thread overview]
Message-ID: <48621B7E.5090600@miraclelinux.com> (raw)
In-Reply-To: <69A5E767EC979846826F566C7932A3F207233B5F@exchange03.iabg.de>

Hi Marcus

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.

> ...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.

I think kernel can solve this problem better.


Regards,
Naohiro Ooiwa


Fey Marcus さんは書きました:
> Hi Naohiro,
> 
>> I'm not convinced yet.
>> I don't think it's correct that kernel or ping6 arbitrarily 
>> decides outgoing interface.
>>
>> Is this really an expected behaviour?
>> Could you explain to me the reason of it, too?
>>
>> I think the behavior should be similar to IPv4.
> 
> It's due to routing.
> 
> Your routing table shows this:
> ---
>     # route -A inet6
>     Kernel IPv6 routing table
>     Destination            Next Hop Flags Metric Ref    Use Iface
>     2001:2c0:418:1::/64    *        U     256    0        0 eth0
>     2001:2c0:418:2::/64    *        U     256    0        0 eth1
>     fe80::/64              *        U     256    0        0 eth0
>     fe80::/64              *        U     256    0        0 eth1
>     ::::::
>     2001:2c0:418:1::1/128  *        U     0      8        1 lo
>     2001:2c0:418:2::2/128  *        U     0      5        1 lo
>     ::::::
>     ff00::/8               *        U     256    0        0 eth0
>     ff00::/8               *        U     256    0        0 eth1
>     #
> ---
> 
> ...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.
> 
> Bye,
> 
> Marcus
> -----------------------------------------
> IABG mbH
> Sitz der Gesellschaft: Ottobrunn, Registergericht: Amtsgericht Muenchen, HRB 5499
> Geschaeftsfuehrung: Prof. Dr.-Ing. Rudolf F. Schwarz
> Vorsitzender des Aufsichtsrats: General a. D. Wolfgang Altenburg
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2008-06-25 10:18 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   ` Naohiro Ooiwa [this message]
2008-06-25 11:26     ` (usagi-users 04056) " Fey Marcus
2008-06-26  0:48       ` Naohiro Ooiwa
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=48621B7E.5090600@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.