[krbdev.mit.edu #8530] KDC/kadmind explicit wildcard listener addresses do not use pktinfo
Richard Basch via RT
rt-comment at krbdev.mit.edu
Mon Dec 26 15:04:33 EST 2016
/etc/sysconfig/network is configured with "NETWORKING_IPV6=no", but I was able to "modprobe ipv6 ; lsmod | grep ipv6". And I 100% agree it is coming from socket()... I said bind not able to come up with the words "opening a socket" at that late hour, but did not mean bind(2); I agree the error occurs during socket(2).
-----Original Message-----
From: Greg Hudson via RT [mailto:rt-comment at krbdev.mit.edu]
Sent: Monday, December 26, 2016 2:28 PM
To: Basch, Richard [Tech]
Subject: [krbdev.mit.edu #8530] KDC/kadmind explicit wildcard listener addresses do not use pktinfo
Our pktinfo support explicitly doesn't operate on non-wildcard sockets (see udppktinfo.c:is_bound_to_wildcard()), and now that I think about it, there may have been some issues trying to use pktinfo on non- wildcard sockets on FreeBSD. So I don't think that test was conclusive.
Also, do you know if the kernel on these machines was built without IPv6 support? I think an EAFNOSUPPORT error would actually come from socket(), not bind().
More information about the krb5-bugs
mailing list