Sent: Thursday, October 19, 2023 at 4:06 PM From: "Matus UHLAR - fantomas" <uh...@fantomas.sk> > > >On Wed Oct 18 09:00:24 UTC 2023, Matus UHLAR wrote: > >> I don't see any explicit option to disable dhcp server, but using > >> --no-dhcp-interface= option or --dhcp-alternate-port could hep you. > > On 19.10.23 14:02, Luigi Baldoni via Dnsmasq-discuss wrote: > >I do not wish to disable the dhcp server, indeed I want to use it. > > why do you run kea dhcp server then?
It's different traffic that I wish to handle separately and it's easier for me this way. > >Applying --no-dhcp-interface for lo and other interfaces did not help. > >Would the dhcp server still work if listening on a different interface? > > yes, that's possible. > option bind-interfaces should fix the problem. That solved the problem with ISC dhcp server, but not with kea. > >> how is it being started? could the startup procedures be protecting the > >> config by rewriting it to a known state during startup? > > >On Wed Oct 18 09:56:49 UTC 2023, wkitty42 wrote: > >Tried init, systemctl (two different debian installations) and invoking the > >daemon straight from console: no change. > > I don't think this will help. Which one? > the problem is that both dnsmasq and kea dhcp server are trying to listen on > port 69. On different interfaces. And it's hard for me to understand why both, or dnsmasq at any rate, attempt to listen on interfaces that are explicitly excluded in the configuration. Regards _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
