[Dnsmasq-discuss] dnsmasq.service: Control process exited, code=exited, status=127/n/a

[Andrew Miskell]

> On Jul 10, 2023, at 3:34 PM, dnsmasqyq.xpt at neverbox.com wrote:
> 
> It's my own problem.
> 
> On Mon, Jul 10, 2023 at 3:57 PM Tong Sun wrote:
> 
>> Sure, but I'd like to rule out that it's because of my own *unusual* use
>> case, that my network device is not eth0 but br0 instead.
>> 
>> And it turns out to be exactly the root cause --
>> 
>> reverting from br0 to eth0 & reboot, then do the following
>> 
>> sudo apt install -y --reinstall dnsmasq-base dnsmasq
>> 
>> and it finished without any issue, while previously it was just impossible.
>> 
>> Ref, switching my network device from eth0 to br0 is done via following
>> https://linuxconfig.org/how-to-use-bridged-networking-with-libvirt-and-kvm
> 
> Hmm... redid my steps in a clean VM and it works just fine. So,
> 
>> I'm now more inclined to think it is dnsmasq's problem, not Debian
>> packaging's problem. Comments?
> 
> It's my own problem.
> 
> Sorry about the noise.
> 
> 
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Were you using a migrated configuration file or a fresh configuration file on the original VM? You might have had a configuration line which was telling dnsmasq to bind to a specific interface and that interface wasn’t available on the system.

I think by default, the configuration file in most packages don’t specify an interface to bind to, so dnsmasq will bind to all available interfaces.