From: James Prestwood <prestwoj@gmail.com>
To: Andrea Pappacoda <andrea@pappacoda.it>, iwd@lists.linux.dev
Subject: Re: MulticastDNS for all connections
Date: Tue, 01 Nov 2022 13:54:36 -0700 [thread overview]
Message-ID: <66b9f15578d9f7112e532a7174268b02b629360f.camel@gmail.com> (raw)
In-Reply-To: <A4TIKR.5DC9OCNE90W6@pappacoda.it>
On Sat, 2022-10-29 at 17:16 +0200, Andrea Pappacoda wrote:
> Hi all!
>
> I have a question regarding the usage of iwd, specifically about the
> MulticastDNS option. Is it possible to enable it for all the
> networks?
>
> The iwd.network(5) manual page mentions that one can enable
> MulticastDNS for a particular network, but it also says that "The
> group
> [Network] contains general network settings and any network specific
> overrides for global defaults defined in the main iwd configuration
> file.". Unfortunately though, setting MulticastDNS=true in
> /etc/iwd/main.conf does not lead to my desired result.
>
> I'm not using neither systemd-networkd, ConnMan nor NetworkManager.
>
> If this is not the most appropriate place where to discuss about
> feature requests, feel free to redirect me to the right place :)
>
> Thanks!
First, I don't know much about mDNS :) but anyways...
Currently the MulticastDNS option is only per-network, but systemd-
resolved has a global setting itself according to the docs [1].
But I actually wonder if event setting MulticastDNS in IWD is doing
anything:
"Multicast DNS will be enabled on a link only if the per-link and the
global setting is on."
This would imply you need to set /etc/systemd/resolved.conf with
MulticastDNS=true to even use mDNS at all? Or maybe you have already
done this? And I see the problem, per-link settings are only in
systemd-networkd, which you don't use...
Like I said, I don't know much about mDNS but would a global option
'break' networks which don't support mDNS? Are you frequently
connecting to many networks and needed to add this option to the
profile each time?
The fact that this depends on setting systemd-resolved's global option
and the per-link option I would say this really should stay in systemd-
* itself. The IWD setting is kinda useless without the global option
anyways. Plus systemd-networkd is much more flexible, you can match
based on all kinds of things where IWD is very rigid (global or per-
network).
[1] https://www.freedesktop.org/software/systemd/man/resolved.conf.html
>
>
>
next prev parent reply other threads:[~2022-11-01 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 15:16 MulticastDNS for all connections Andrea Pappacoda
2022-11-01 20:54 ` James Prestwood [this message]
2022-11-02 20:23 ` Andrea Pappacoda
2022-11-02 20:47 ` James Prestwood
2022-11-02 21:55 ` Andrea Pappacoda
2022-11-02 22:06 ` James Prestwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66b9f15578d9f7112e532a7174268b02b629360f.camel@gmail.com \
--to=prestwoj@gmail.com \
--cc=andrea@pappacoda.it \
--cc=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).