Peter Palfrader wrote:
> knot does not listen on all configured addresses after system boot.
Hi, Peter:
This sounds like knot is being started before DAD completes on the
interface. But I was under the impression this was fixed in ifupdown
with the fix for #705996. Does 'journalctl -b -u networking.service'
show a "Waiting for DAD" message like this?
root@li:~# journalctl -b -u networking.service
-- Logs begin at Wed 2016-12-28 14:39:21 EST, end at Sun 2017-07-09
16:08:32 EDT. --
Jul 09 16:08:01 li systemd[1]: Starting Raise network interfaces...
Jul 09 16:08:02 li ifup[559]: Waiting for DAD... Done
Jul 09 16:08:02 li systemd[1]: Started Raise network interfaces.
root@li:~#
The version of knot that you're using will attempt to perform a
non-local bind on the UDP socket, but not the TCP socket, which is
pending an upstream fix:
https://gitlab.labs.nic.cz/labs/knot/merge_requests/740
But the non-local bind shouldn't be necessary in the first place, hm.
Just in case, can you also verify that knot is definitely being started
after networking has been brought up? Something like:
journalctl -b -o short-monotonic -u networking.service -u knot.service
should show it.
--
Robert Edmonds
edmo...@debian.org
