From: carbonchauvinist@protonmail.ch
To: iwd@lists.01.org
Subject: Re: Issue with iwd 1.3 + systemd-resolved + iwd's built-in network configuration not adding DNS servers
Date: Mon, 16 Dec 2019 21:37:15 +0000 [thread overview]
Message-ID: <20191216213715.2770.68692@ml01.vlan13.01.org> (raw)
In-Reply-To: <20191216074839.2770.41114@ml01.vlan13.01.org>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
I've run into this issue as well with 1.3. I'm using iwd + systemd-resolved (using iwd to manage the network, i.e. no systemd-networkd at play here).
From what I can tell it's due to the fact that commit 930528e35 appends domain names as routing-only domains (i.e. prepends with "~"). I have "lan" as the domain value in my router and this is in turn added as "~lan" when viewing the output with resolvectl status. This changes the way systemd-resolved sets the "DefaultRoute" value and causes it to be false instead of true.
Currently I can either manually, and non-permanently, set the DefaultRoute to true on the link in order to get name resolution (i.e.: `# resolvectl default-route wlan0 1`) or I can remove the domain designation from my router/dhcp server.
I wonder if the goal was to add the domains as routing-only domains instead of search-domains? (https://www.freedesktop.org/software/systemd/man/systemd.network.html#Domains=)
Because I'm not using systemd-networkd I don't know/see a way to override the DefaultRoute value permanently, though I obviously could be missing something.
next prev parent reply other threads:[~2019-12-16 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 7:48 Issue with iwd 1.3 + systemd-resolved + iwd's built-in network configuration not adding DNS servers caljorden
2019-12-16 21:37 ` carbonchauvinist [this message]
2019-12-16 21:52 ` carbonchauvinist
2019-12-16 22:23 ` Denis Kenzior
2019-12-17 0:49 ` carbonchauvinist
2019-12-17 5:07 ` caljorden
2019-12-17 17:05 ` Denis Kenzior
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=20191216213715.2770.68692@ml01.vlan13.01.org \
--to=carbonchauvinist@protonmail.ch \
--cc=iwd@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.