netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] IPv6:fix the return interface index when get it while no message is received
Date: Wed, 20 Aug 2008 10:56:30 +0800	[thread overview]
Message-ID: <48AB87DE.1010205@cn.fujitsu.com> (raw)
In-Reply-To: <48AACC71.5090701@hp.com>

Vlad Yasevich wrote:
> Yang Hongyang wrote:
>> David Miller wrote:
>>> From: Vlad Yasevich <vladislav.yasevich@hp.com>
>>> Date: Mon, 18 Aug 2008 09:31:07 -0400
>>>
>>>> I don't think that's correct at all.  The code path shows here is
>>>> when there are no received options and no sticky options set.  In
>>>> such case, we shouldn't be returning multicast or bound interfaces.
>>>> We should be returning 0.
>> I use setsockopt() to set the bounded interface of the socket, and 
>> then I get receiving interface index while no message is received through
>> the above socket,shoudn't the bounded interface be returned?
> 
> One of the problems is that we don't seem to support the sticky IPV6_PKTINFO
> option as specified in rfc3542.
> 
> The setting of SO_BINDTODEVICE should not impact the return of the sticky option
> values when they are not set.  A return of 0 in the sticky options means that
> that value has not been specified.  If you return anything else, you give
> the illusion that a sticky option was set.
> 
>>>> Additionally the address returned is completely bogus as well. We
>>>> are returning the address our peer instead of the one of our own
>>>> addresses.
>> If message is received,the address returned is what the received
>> message refered to, otherwise the address returned is what I used setsockopt()
>> to set before.
> 
> We are returning np->daddr, which is the peer address.
> 
> The expected value is "destination of the received packet".  In the worst case,
> it should be the locally bound address.  In the correct case, it should be the
> address set in the sticky options if such is set.  It really should be 0::0, if there
> are no sticky options and no packets have been received.

Since here we do not recive any packet,we should return 
src_info.ipi6_ifindex=0 and src_info.ipi6_addr=0::0,right?

> 
> -vlad
> 
>>> Yang, please fix this up, thank you.
>>>
>>>
>> Seems that I misunderstood the RFC?




  reply	other threads:[~2008-08-20  2:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  6:07 [PATCH] IPv6:fix the return interface index when get it while no message is received Yang Hongyang
2008-08-18  6:22 ` David Miller
2008-08-18 13:31 ` Vlad Yasevich
2008-08-19  5:38   ` David Miller
2008-08-19  6:28     ` Yang Hongyang
2008-08-19 13:36       ` Vlad Yasevich
2008-08-20  2:56         ` Yang Hongyang [this message]
2008-08-20 13:10           ` Vlad Yasevich
2008-08-22 11:54             ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-08-08  4:27 get receiving interface index " Yang Hongyang
2008-08-08  5:59 ` [PATCH] IPv6:fix the return interface index when get it " Yang Hongyang
2008-08-08  6:03   ` David Miller
2008-08-08 14:58     ` Vlad Yasevich
2008-08-18  5:41       ` 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=48AB87DE.1010205@cn.fujitsu.com \
    --to=yanghy@cn.fujitsu.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=vladislav.yasevich@hp.com \
    --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).