The regression test SetTTLAndGetTTL is failing on IPv6
system because it tries to set the TTL to (byte)200. A byte
is signed but this is really trying to set the TTL to -56.
The IPv4 socket option IP_MULTICAST_TTL doesn't complain
about a negative value but the IPv6 option IPV6_MULTICAST_HOPS
does not like a negative value.
The issue of course relates to sins of the past whereby the
setTTL has a byte argument rather than an int.
system because it tries to set the TTL to (byte)200. A byte
is signed but this is really trying to set the TTL to -56.
The IPv4 socket option IP_MULTICAST_TTL doesn't complain
about a negative value but the IPv6 option IPV6_MULTICAST_HOPS
does not like a negative value.
The issue of course relates to sins of the past whereby the
setTTL has a byte argument rather than an int.