NM, dnsmasq & systemd-resolved...

[Marco Moock]

Am 29.07.2025 um 21:10:18 Uhr schrieb Petr Menšík:

> I think this comes from the NM plugin code for dnsmasq [1]. This is
> to avoid listening on all addreses on lo interface. This specifies
> only IPv4 localhost, not IPv6 localhost address, because there is
> reasonable assumption it is always present.

Why is it reasonable to assume IPv4 localhost exists? Where is the
difference to IPv6? Both protocols are enabled by default in the kernel
an can be disabled. The only reasonable check would be to test if those
addresses exist and if so, listen on them.

> If there was just --interface=lo, it may listen also on ::1 and any 
> additional addresses present on the interface. Which is not wanted
> usually.

Why?

> You can add any extra interfaces or addresses to listen on in
> additional config file. But sadly there is no simple way to suppress
> 127.0.0.1 what were already explicitly given on the command line.

That is stuff that needs to be addressed by NM if it starts up dnsmasq.

> There is no simple way to listen on both 127.0.0.1 and ::1 if
> present, but continuing in case of ::1 is missing. Therefore it does
> not listen on ::1 from NM, but usually does when started from
> separate systemd service. Makes dig @localhost print errors, but I do
> not know any nice solution working always.

Would it be possible to let NM check the existence of both addresses
and then craft the right command?

-- 
Gruß
Marco

Send unsolicited bulk mail to 1753816218muell at cartoonies.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/networkmanager/attachments/20250729/620dc4ac/attachment.sig>