diff options
| author | James Clarke <jrtc27@jrtc27.com> | 2017-10-07 18:53:23 +0100 |
|---|---|---|
| committer | Denys Vlasenko <vda.linux@googlemail.com> | 2017-10-30 16:06:50 +0100 |
| commit | 518fb3ba193cddc1369090bfdf827618b42791db (patch) | |
| tree | 437b68db12aaa6910a1f2d717f2374c5ad78acb7 /libbb/last_char_is.c | |
| parent | d1535216ca27047e3962d61b975bd2a638aa45a2 (diff) | |
| download | busybox-518fb3ba193cddc1369090bfdf827618b42791db.tar.gz | |
udp_io, traceroute: Standardise IPv6 PKTINFO handling to be portable
The current standard (RFC 3542) is for IPV6_RECVPKTINFO to be given to
setsockopt, and IPV6_PKTINFO to be used as the packet type. Previously,
RFC 2292 required IPV6_PKTINFO to be used for both, but RFC 3542
re-purposed IPV6_PKTINFO when given to setsockopt. The special
Linux-specific IPV6_2292PKTINFO has the same semantics as IPV6_PKTINFO
in RFC 2292, but was introduced at the same time as IPV6_RECVPKTINFO.
Therefore, if we have IPV6_RECVPKTINFO available, we can use the RFC
3542 style, and if not, we assume that only the RFC 2292 API is
available, using IPV6_PKTINFO for both.
Signed-off-by: James Clarke <jrtc27@jrtc27.com>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'libbb/last_char_is.c')
0 files changed, 0 insertions, 0 deletions