netdev - IPv6 Destination Options question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5975583.vpC7qLWE0j@cg-notebook>
Date:   Sat, 14 Dec 2019 17:11:15 +0100
From:   Christoph Grenz <christophg+lkml@...nz-bonn.de>
To:     netdev@...r.kernel.org
Subject: IPv6 Destination Options question

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