From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: Octavian Purdila <opurdila@ixiacom.com>
Cc: netdev@vger.kernel.org
Subject: Re: question regarding (AF_INET6, SOCK_RAW, IPPROTO_RAW) sockets
Date: Wed, 12 Mar 2008 20:06:48 +0200 [thread overview]
Message-ID: <200803122006.49506.rdenis@simphalempin.com> (raw)
In-Reply-To: <200803121834.29293.opurdila@ixiacom.com>
Le Wednesday 12 March 2008 18:34:29 Octavian Purdila, vous avez écrit :
> Hi,
>
> I've noticed that when using IPv6 raw sockets with IPPROTO_RAW protocol and
> IPV6_PKTINFO set, we are not allow to specify a source address that it is
> not configured in the system.
>
> Disabling ipv6_chk_addr in datagram_send_ctl for IPv6 raw sockets seems to
> fix our problem. Is this approach the right one?
I am a bit confused here. Why would you use IPV6_PKTINFO with a network-layer
raw socket? You have to write the IPv6 header anyway, so what useful
additional infos would you the ancillary data contain?
--
Rémi Denis-Courmont
next prev parent reply other threads:[~2008-03-12 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 16:34 question regarding (AF_INET6, SOCK_RAW, IPPROTO_RAW) sockets Octavian Purdila
2008-03-12 18:06 ` Rémi Denis-Courmont [this message]
2008-03-12 23:02 ` Octavian Purdila
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=200803122006.49506.rdenis@simphalempin.com \
--to=rdenis@simphalempin.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
/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).