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: Why can't connman automatically enable and connect to cellular
network interface?
(JH)
2. RE: [PATCH v2 0/3] Simplify settings save code (Thomas Green)
----------------------------------------------------------------------
Date: Mon, 6 Jan 2020 20:57:04 +1100
From: JH <[email protected]>
Subject: Re: Why can't connman automatically enable and connect to
cellular network interface?
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<CAA=hcwqaash6da8djrj9ganx_ktxwm9wgxmmt2jvf_zmjgu...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
I looked back your advice that "any new cellular network would
autoconnect without interaction of the user", could you elaborate how
I can set up new cellular network for autoconnect?
I have recently changed SIM and also cellular network, the original
SIM used Telstra cellular network, I defined Name = Telstra in
cellular.config, that worked fine.
Now I changed the SIM to Aeris, it does not have MNO but using ASN =
iot-eu.aer.net, everything stopped working.
I am always wondering why I should define cellular network name in
cellular.config, but apparently that is not an option, without the
cellular network name in cellular.config, it just could noit work. Why
can't connman and ofono automatically connecting to cellular network
based on SIM and network registration?
Thank you.
Kind regards,
- jh
On 4/24/19, Daniel Wagner <[email protected]> wrote:
> On 4/23/19 9:22 AM, Christophe Ronco wrote:
>> On 4/21/19 7:56 PM, Tarmo Kuuse wrote:
>>> On 21.04.19 10:02, JH wrote:
>>>> I installed oFono plugin to an embedded system where the cellular is
>>>> used, I suppose that the connman should automatically enable and
>>>> connect to cellular when it first time boot up, it didn't, I have to
>>>> manually run the connmanctl command to enable and to connect it. In a
>>>> product due to limited Flash storage size, I'll not install connmanctl
>>>> and there will be no manual interactive process, how can I set up
>>>> connman to automatically enable and connect to cellular network
>>>> interface?
>>>
>>> I second this question. With a blank device out of manufacturing, how
>>> would I configure connman to automatically bring up the cellular
>>> connection? There is no possibility for the user to interact with the
>>> device, so cellular should just connect as long as any working SIM is
>>> installed. Assume the SIM is 100% good to go - no PIN, APN/user/pass
>>> present in mobile-broadband-provider-info, etc.
>
> As it stands today you would deploy a /var/lib/connman/settings with the
> correct settings.
>
>> 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?
>
> 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.
>
> Thanks,
> Daniel
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
>
------------------------------
Date: Mon, 6 Jan 2020 20:59:30 +0000
From: Thomas Green <[email protected]>
Subject: RE: [PATCH v2 0/3] Simplify settings save code
To: Daniel Wagner <[email protected]>, "[email protected]"
<[email protected]>
Message-ID: <CY4PR0401MB36658454751F30623C235D139F3C0@CY4PR0401MB3665
.namprd04.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Daniel,
Sorry I was out so long. I was having shoulder surgery. I'm back now. I've
applied this patch and testing it in the use case we were looking at. Now,
when at the end of the use case, the settings file for the ethernet controller
have
IPv4.method=manual
But have saved none of the IPv4 information, so any attempt to reconnect to the
ethernet fails with an Input/Output error.
Any clues where to go to from here?
Tom
-----Original Message-----
From: Daniel Wagner <[email protected]>
Sent: Wednesday, January 1, 2020 8:23 AM
To: [email protected]
Cc: Daniel Wagner <[email protected]>
Subject: [PATCH v2 0/3] Simplify settings save code
[EXTERNAL]
Start with an empty kefile for storing the current configuration. Thus we can
drop the configuration update code. While at it also refactor the keyfile code
in ipconfig and save around 1k of code.
Daniel Wagner (3):
service: Store configuration in empty keyfile
ipconfig: Refactor keyfile store and load operations
storage: Remove unused __connman_storage_open_service()
src/connman.h | 5 +-
src/ipconfig.c | 269 ++++++++++++++++++++++++++-----------------------
src/service.c | 59 ++++-------
src/storage.c | 22 ----
4 files changed, 161 insertions(+), 194 deletions(-)
--
2.24.1
_______________________________________________
connman mailing list -- [email protected] To unsubscribe send an email to
[email protected]
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 51, Issue 6
**************************************
