All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-ppp@vger.kernel.org
Subject: Re: RFC: support setting DNS for systemd-resolved via DBus
Date: Tue, 04 Sep 2018 13:06:17 +0000	[thread overview]
Message-ID: <7649.1536066377@localhost> (raw)
In-Reply-To: <e5fa9fe1-073c-e9c5-c774-21bc5487fe7e@iam.tj>

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


Tj <linux@iam.tj> wrote:
    > I've recently been building an embedded device to do (kernel-mode)
    > PPPoE which uses only systemd-networkd + systemd-resolved (PC Engines
    > APU2 with Ubuntu 18.04 - amd64).

...

    > After some experimentation I've put together a small C helper program
    > that reads DNS[12]= from the helper environment and uses DBus calls to
    > set the per-link nameservers.

It seems like if small is your goal that you ought to have the ppp client do
this directly.

    > It build-depends on libdbus but not systemd.

Cool.

    > I'm looking for feedback on whether this would be acceptable as an
    > addition to the ppp project, and if so where in the source tree would
    > be appropriate.

I would add it to ppp, and I'd put it into src/dbusdns.c or some such named
code.

If standalone, then give it a new directory.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-09-04 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 10:17 RFC: support setting DNS for systemd-resolved via DBus Tj
2018-09-04 13:06 ` Michael Richardson [this message]
2018-09-04 13:22 ` Marco d'Itri

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=7649.1536066377@localhost \
    --to=mcr@sandelman.ca \
    --cc=linux-ppp@vger.kernel.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.