On Sat, 5 Sep 2015, Kevin Otte wrote:
> krb5kdc fails to bind to the IPv6 addresses on the system at startup.
> Workaround is a manual service restart on every boot.
It seems that this is fallout from systemd's ideas about starting up the
network, since the KDC just loops over the available
This ought to work, but there might be something going wrong with
routing socket updates.
Because krb5kdc implements a UDP service, it needs to either use
IPv4/IPv6 pktinfo support, or bind to specific interfaces instead of the
wildcard address, in order to send replies from the same address as
Package: krb5-kdc
Version: 1.12.1+dfsg-19
Severity: important
Tags: ipv6
krb5kdc fails to bind to the IPv6 addresses on the system at startup.
Workaround is a manual service restart on every boot.
root@mercury:~# uptime
14:08:38 up 0 min, 1 user, load average: 0.69, 0.19, 0.06
root@mercury:~#
3 matches
Mail list logo
