Thread (2 messages) flat view 2 messages, 2 authors, 2018-01-25

Re: [PATCH net-next] ipv6: raw: use IPv4 raw_sendmsg on v4-mapped IPv6 destinations

From: David Miller <davem@davemloft.net>
Date: 2018-01-25 17:07:13

From: Ivan Delalande <redacted>
Date: Wed, 24 Jan 2018 17:43:43 -0800
Make IPv6 SOCK_RAW sockets operate like IPv6 UDP and TCP sockets with
respect to IPv4 mapped addresses by calling IPv4 raw_sendmsg from
rawv6_sendmsg to send those messages out.

Signed-off-by: Travis Brown <redacted>
Signed-off-by: Ivan Delalande <redacted>
For RAW sockets this doesn't make any sense.

Especially when header-include is enabled, one expects the application
to provide an address-family appropriate protocol header in it's
buffer.

Which means ipv4 for ipv4 sockets and ipv6 for ipv6 sockets.

So we should interpret the request as an ipv6 one regardless of
whether the ipv6 destination is ipv4 mapped or not.

Thank you.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help