public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Grenz <christophg+lkml@grenz-bonn.de>
To: netdev@vger.kernel.org
Subject: IPv6 Destination Options question
Date: Sat, 14 Dec 2019 17:11:15 +0100	[thread overview]
Message-ID: <5975583.vpC7qLWE0j@cg-notebook> (raw)

Hello,

I'm playing around with Mobile IPv6 and noticed a strange behaviour in the 
Linux network system when using IPv6 destination options:

I'm able to send destination options on SOCK_DGRAM and SOCK_RAW sockets with
sendmsg() and IPV6_DSTOPTS ancillary data. The sent packets also look correct 
in Wireshark.

But I'm not able to receive packets with destination options on a socket with 
the IPV6_RECVDSTOPTS socket option enabled. Both a packet with a Home Address 
Option and a packet with an empty destination options header (only containing 
padding) won't be received on a socket for the payload protocol.

Only a SOCK_RAW socket for IPPROTO_DSTOPTS receives the packet.

I tested this on a vanilla 5.4.0 kernel and got the same behaviour. Activating 
dyndbg for everything in net/ipv6 didn't produce any relevant output in dmesg.

Is this expected behaviour or a bug? Or do I maybe need some other socket 
option or a xfrm policy to receive packets with destination options?

Best regards
Christoph


             reply	other threads:[~2019-12-14 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 16:11 Christoph Grenz [this message]
2019-12-14 20:40 ` IPv6 Destination Options question Tom Herbert
2019-12-14 21:11   ` Christoph Grenz
2019-12-16  1:59     ` Christoph Grenz

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=5975583.vpC7qLWE0j@cg-notebook \
    --to=christophg+lkml@grenz-bonn.de \
    --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