Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, 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: Why can't connman automatically enable and connect to
cellular network interface? (JH)
2. Re: The DHCP/DNS confusion (aka no-one cares about
/etc/resolv.conf) ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Apr 2019 21:13:21 +1000
From: JH <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: Christophe Ronco <[email protected]>, [email protected]
Subject: Re: Why can't connman automatically enable and connect to
cellular network interface?
Message-ID:
<CAA=hcWSD-zpCwHzqCvdYuL=E58Bwu2F2s=g2c6mgv6+twqi...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
> As it stands today you would deploy a /var/lib/connman/settings with the
> correct settings.
I deployed /var/lib/connman/settings,
/var/lib/connman/cellular_505013520350165_context1 and
/var/lib/connman/wifi_d4ca6e001bc0_5450472d4d434e46_managed_psk,
nothing works without manually running the connmanctl configure. This
is a very basic feature, all documents pointed it should be
automatically notified and configured, I don't think it only works in
the latest version 1.36. What I could be missing? I am running 1.35 on
imx6 EVK.
>> I resolved this problem some time ago by telling that cellular services
>> are favorite (like Ethernet services). I use this patch with connman
>> 1.36. Here is the patch comment:
>>
>> [connman] autoconnect cellular service when SIM is not known (#07397)
>>
>> Add a patch to connnman to make cellular services favorite (like
>> ethernet
>> services). This allow "unknown" cellular services to be
>> autoconnected.
>> Concretely, when a SIM is used for the first time on a board,
>> cellular service
>> will be autoconnected by connman if there is no ethernet cable
>> plugged in.
>>
>>
>> Maybe this could be integrated in upstream connman with a configuration
>> in main.conf?
I deployed your patch, it still did not work, do I need to make
changes in main.conf?
> While this works for your setup, it has unwanted side effects. Such as
> any new cellular network would autoconnect without interaction of the
> user. Ethernet is different in this regard because the user already told
> use the indent. He plugged the cable into the device.
>
> I am not against changing this stuff, I am just pointing out this needs
> more then just marking the cellular technology per default as auto
> connectable.
Should the default network connection follows PreferredTechnologies =
ethernet,wifi,cellular? Correct me if I am wrong, I thought
autoconnect feature is different to the network connection priority in
main.conf. If I define the priority in PreferredTechnologies, no user
intervention should be required.
Thank you.
Kind regards,
- jupiter
------------------------------
Message: 2
Date: Wed, 24 Apr 2019 20:55:44 +0200
From: <[email protected]>
To: [email protected], Daniel Wagner <[email protected]>
Subject: Re: The DHCP/DNS confusion (aka no-one cares about
/etc/resolv.conf)
Message-ID: <20190424205544.4ae4a41d@huit>
Content-Type: text/plain; charset=US-ASCII
Hi Daniel,
OK... through the post of Doron Behar "duplicate entries
in /etc/resolv.conf" I understand now ;)
But it would really be helpful for others to have "resolv.conf" appear
in the man page (under FILES) to let people know, that connman actually
creates a /var/run/connman/resolv.conf ... and this seemingly
independent of the --nodnsproxy parameter. - Is that correct ?
Because NetworkManager manipulates /etc/resolv.conf directly and one
can't guess that there is a /var/run/connman/resolv.conf... or did I
still miss something ?
And I can +1 the duplicate entries within /var/run/connman/resolv.conf.
'cause mine looks like this:
# Generated by Connection Manager
search fritz.box fritz.box fritz.box fritz.box fritz.box fritz.box
nameserver 192.168.43.1
Please let me know if you might need additional info in order to
hunt this bug down.
Knuth
--
On Tue, 23 Apr 2019 13:57:53 +0200 <[email protected]>
wrote:
> Hi,
>
> I am having a knot in my brain ;) ... please help:
>
> Who is handeling dhcp requests with connmand?
>
> Now I would have thgought:
> (a) either wpa_supplicant and/or connman
> run dhcpcd or dhclient or pump once a physical layer link is
> established ... and they would update/touch /etc/resolv.conf if they
> received a DNS server via DHCP
>
> (b) or does connmand handles dhcp itself
>
> // But if it's (a):
> I don't see any trace in the log of connmand doing so and
> I just removed /etc/resolv.conf and connected to wifi network and
> no /etc/resolv.conf got created.
>
> // But if it's (b):
> I did not see anything in the log of connmand doing so and
> there seems only the --nodnsproxy parameter... which does
> not help me solve my problem either, because I not want to use
> the internal DNS proxy but still have /etc/resolv.conf
> configured.
>
> So I am lost.
>
> I am
> using: /etc/systemd/system/connman.service.d/disable_dns_proxy.conf
> (so connmand is running as `/usr/bin/connmand -n --nodnsproxy`)
>
> Do I then need something like systemd-resolved ??
> Or maybe I am missing something super obvious ?
>
> It would be helpful if the output of connmand -n would talk about DNS
> server / DHCP / resolv.conf... but if I did not miss it, there was
> nothing.
>
> Reason I am asking: I would like that /etc/resolv.conf get's created
> when connecting (via wpa_supplicant) to wireless network which sends a
> specific DNS server for this wifi network (e.g. for local
> 'login'/'authenication' via web-browser).
>
>
> Thanks a lot for helping me remove the fog I am in :)
>
> Tormen
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 42, Issue 20
***************************************
