From: Paul Rolland <rol@as2917.net>
To: netdev@vger.kernel.org
Subject: IPv6 raw socket and recvfrom
Date: Tue, 17 Aug 2010 14:31:20 +0200 [thread overview]
Message-ID: <20100817143120.7fad5186@tux.DEF.witbe.net> (raw)
Hello,
I'd like someone to clarify the behavior I can expect from a RAW IPv6
socket _in Linux_ :
- Raw IPv4 sockets : recvfrom() payload contain all the IP header,
including src ip, dst ip, etc...
- Raw IPv6 sockets : so far, recvfrom returns me only the payload. I've
added the HDRINCL options, but it seems that this is a no-op in
IPv6-land.
I've reviewed RFC 3542, which states that I'm not to expect ip6 header, but
often "there is more than one way to do it", and I'd like to be sure I'm
not missing something obvious
Paul
PS : I'm not subscribed to netdev, so please answer directly...
next reply other threads:[~2010-08-17 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 12:31 Paul Rolland [this message]
2010-08-17 13:08 ` IPv6 raw socket and recvfrom Rémi Denis-Courmont
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=20100817143120.7fad5186@tux.DEF.witbe.net \
--to=rol@as2917.net \
--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 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).