Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: if-up if-down scripts or systemd network-online target
([email protected])
2. Nameservers and FallbackNameservers ([email protected])
----------------------------------------------------------------------
Date: Tue, 22 Oct 2019 17:26:37 +0200
From: <[email protected]>
Subject: Re: if-up if-down scripts or systemd network-online target
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID: <20191022172637.6562400c@huit>
Content-Type: text/plain; charset=US-ASCII
Hi Daniel,
thanks a lot!
I will try to dig into that :)
Also: I would like to help improve the documentation of connman.
I will try to provide patches for the man-pages ... have to see how
writing man-pages works in detail ;)
*Is that something that you / the connman maintainers would welcome ?*
Once I unstdood the purpose and
capabilities/design of connman-wait-online.service I will try
to add some info about it so that people will find it if they
want to run a script once an interface is brought ht up (configured) or down.
But I also see other deficites but will write a new post with a new
subject with other questions about this right after.
Cheers,
Tormen
--
On Mon, 21 Oct 2019
09:58:19 +0200 Daniel Wagner <[email protected]> wrote:
> Hi Tormen,
>
> On Thu, Oct 17, 2019 at 08:45:13PM +0200, [email protected] wrote:
> > So if connman would
> > * start network-online when AT LEAST ONE interface is
> > brought up and would
> > * stop network-online when the LAST interfaces would be
> > brought down
> > then this could IMHO satisfy most cases for if-up if-down scripts.
> >
> > What say you? :)
>
> If I understood you correctly, there is already the
> connman-wait-online.service script which is what you request:
>
>
> $ cat src/connman-wait-online.service
> [Unit]
> Description=Wait for network to be configured by ConnMan
> Requisite=connman.service
> After=connman.service
> Before=network-online.target
> DefaultDependencies=no
> Conflicts=shutdown.target
>
> [Service]
> Type=oneshot
> ExecStart=/usr/sbin/connmand-wait-online
> RemainAfterExit=yes
>
> [Install]
> WantedBy=network-online.target
>
>
> Thanks,
> Daniel
--
------------------------------
Date: Tue, 22 Oct 2019 22:21:06 +0200
From: <[email protected]>
Subject: Nameservers and FallbackNameservers
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID: <20191022222106.4e887ed3@huit>
Content-Type: text/plain; charset=US-ASCII
Hi Daniel,
two things:
1) A question about how FallbackNameservers are used
2) A question / potential feature request
// 1) A question about how FallbackNameservers are used:
as I just mentioned: I would love to help improving the documentation
for now bit by bit as I am concerned.
As an example I just stumbled about:
* FallbackNameservers in the connman.conf (5) man page
What I miss: You don't explain when this is actually used... I have a
theory, but it would be nice to explicitely state that for the user
IMHO.
As I read in man comman:
Depending on how ConnMan is compiled, it will by default direct all DNS
traffic to itself by setting nameserver to 127.0.0.1 in
resolv.conf(5) file or leave DNS management to an external entity, such
as systemd-resolved.
So I suspect about FallbackNameservers:
======================================================
FallbackNameservers are used in case ConnMan
internally handles DNS management (see --nodnsproxy and man connman how
to change this default behaviour). This variable allows to specify a
comma separated list of nameservers that will be questioned once the
DNS server(s) received via DHCP were consulted first.
======================================================
Is this correct?
// 2) A question / potential feature request
I would /love/ to be able to use my OWN dns server and only as a
Fallback use the DNS servers provided by the DHCP response that connman
handles.
But why do I want that???
I am privacy aware and don't like to
give metainformation like all of my DNS requests to some company /
provider...
Hence I run dnsmasq using a local powerDNS recursor service as upstream
nameserver.
But also more and more people I know setup the DNS to be 1.1.1.1 (to
not use google's 2.2.2.2, 4.4.4.4, 8.8.8.8 servers ;)).
The problem: Some wifi-hotspots have their own custom DNS entries to
e.g. resolve the login URL! (e.g. often in hotels or with the public
transportation wifi hotspot)
So in this case and just for resolving this 1 or 2 URLs I need the DNS
server provided by DHCP.
I can think of 3 implementations but I have the feeling there should be
a more elegant solution, which I was not able to think of yet ;)
a) Provide a way to define default setting for new wifi connections.
And by default I can set the nameserver for this connection to
127.0.0.1 (pointing to my local dnsmasq). And then for connections
where this does not work, I could then leave the nameserver setting
blank / remove that setting so that it uses the connman default
nameserver settings (e.g. the nameserver received via DHCP)
b)
So I could imagine connman setting up 127.0.0.1:53 and then providing a
possibility to set the Nameservers to use to my ip(s)
and then provide the possibility to set the FallbackNameserves to
"DHCP". Meaning it would put whatever DNS servers connman received over
DHCP there.
c)
connman would the nameservers that connman received via DHCP (e.g. in a
/var/lib/connmand/dhcp-resolv.conf or something like that ;))
So that then I can try to figure out a way to point my DNS service
(dnsmasq) to them as fallback...
Tormen
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 48, Issue 29
***************************************
