From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: gerrit@erg.abdn.ac.uk
Cc: davem@davemloft.net, netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH]: Can not set the IPV6_PKTINFO option
Date: Mon, 16 Jul 2007 22:07:30 +0900 (JST) [thread overview]
Message-ID: <20070716.220730.18710682.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20070716.215605.106156812.yoshfuji@linux-ipv6.org>
In article <20070716.215605.106156812.yoshfuji@linux-ipv6.org> (at Mon, 16 Jul 2007 21:56:05 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> says:
> In article <200707161341.23419@strip-the-willow> (at Mon, 16 Jul 2007 13:41:23 +0100), Gerrit Renker <gerrit@erg.abdn.ac.uk> says:
>
> > [IPv6]: Can not set the IPV6_PKTINFO option
> >
> > The Linux manpage of ipv6(7) mentions the IPV6_PKTINFO option (and it is defined in header
> > files), but there is no setsockopt support for it. Aliasing to IPV6_RECVPKTINFO fixes this,
> > and checking datagram_recv_ctl() in net/ipv6/datagram.c confirms that this works as
> > expected from the API.
> >
> > Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
>
> NAK. It is obsolete.
I meant, the manpage is outdated.
Current IPV6_PKTINFO is not equal to IPV6_RECVPKTINFO
but a sticky option to set source address / interface
for outgoing packet.
--yoshfuji
next prev parent reply other threads:[~2007-07-16 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 12:41 [PATCH]: Can not set the IPV6_PKTINFO option Gerrit Renker
2007-07-16 12:56 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-16 13:07 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2007-07-16 13:38 ` Gerrit Renker
2007-07-16 14:02 ` Herbert Xu
2007-07-16 14:14 ` Gerrit Renker
2007-07-16 14:25 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-16 14:17 ` YOSHIFUJI Hideaki / 吉藤英明
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=20070716.220730.18710682.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=gerrit@erg.abdn.ac.uk \
--cc=netdev@vger.kernel.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.