I have took a look inside into nss-mdns. Its implementation just forwards queries name to avahi daemon, but does not send actual packets right from plugin. I guess avahi might receive instructions to disable/enable interfaces via dbus or more advanced method. It already contains ability to exclude or include selected interfaces. But I am not sure if it supports modification of that list runtime.

So at least for mdns the proper solution would be in avahi-daemon.

On 03. 06. 22 19:11, Thomas Haller wrote:

On Fri, 2022-06-03 at 13:55 +0200, Petr Menšík via networkmanager-list
As this is run-time configuration, maybe it should be the ifindex. The
ifindex tends to uniquely identify an interface. Not completely, if the
signed 32 number wraps or if you move interfaces between namespaces,
but still. On the other hand, interfaces can be renamed.


There are problably some conflicting requirements. E.g. the file should
be simple to parse, but also be expressive and extensible with future
features. Making it fully general (instead of specific only to nss-
mdns) makes it potentially more useful. But it also makes it harder to
design future proof.
It sounds like a good idea to me.

Who would define this API? What does
https://github.com/lathiat/nss-mdns think about this? :)

Thank you for reaching out!!

Petr Menšík
Software Engineer, RHEL
Red Hat, http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB

networkmanager-list mailing list

Reply via email to