All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rhys Perry <rhysperry111 at gmail.com>
To: iwd at lists.01.org
Subject: Re: [Feature discussion] Allow overriding of network-specific options globally
Date: Sat, 15 Jan 2022 16:24:19 +0000	[thread overview]
Message-ID: <CAGTBY+ucQ_kWfzxrZaaeL233-Xp28Cq9Kyor_Y+NeCNbGqDqcA@mail.gmail.com> (raw)
In-Reply-To: a1de824d-e923-11d4-96c7-bba662c70843@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

On Fri, 14 Jan 2022 at 18:55, Denis Kenzior <denkenz(a)gmail.com> wrote:
> > I am proposing the ability to override network specific options (ones
> > documented in `iwd.network`) globally. This would be implemented by
>
> I suspect only a subset of these options would make sense to be global.  DNS
> would be one of them.

Yeah, that's fair. I kinda thought that'd be the case, but wasn't sure
what the people over here's thoughts would be

> I'm not sure that adding yet another config file is worthwhile.  We already have
> some network configuration related options in main.conf.  MulticastDNS for
> example.  So I'd start by adding global DNS preference settings there first.

Right- My programming skills aren't the best, but I'll give it a go
:). Where do you think the DNS option should go in the main config
file? Something like `DNSv4` and `DNSv6` in the `Network` section, or
should the `IPv4` and `IPv6` sections be added, each with their own
respective `DNS` entries?

Also, apologies to Denis for accidentally doing a reply instead of a
reply-all initially, I don't participate in mailing lists that often.

Rhys

             reply	other threads:[~2022-01-15 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 16:24 Rhys Perry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-18 15:07 [Feature discussion] Allow overriding of network-specific options globally Denis Kenzior
2022-01-14 18:55 Denis Kenzior
2022-01-14 10:14 Rhys Perry

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=CAGTBY+ucQ_kWfzxrZaaeL233-Xp28Cq9Kyor_Y+NeCNbGqDqcA@mail.gmail.com \
    --to=unknown@example.com \
    /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.