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. Auto-connecting GSM/3G data when roaming (Tarmo Kuuse)
2. IP Pool collision resolution not working when two
technologies tethered (Nuno Gon?alves)
----------------------------------------------------------------------
Message: 1
Date: Tue, 23 Jul 2019 15:12:24 +0300
From: Tarmo Kuuse <[email protected]>
To: [email protected]
Subject: Auto-connecting GSM/3G data when roaming
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi!
I'd like for my device to automatically connect to 3G data in roaming
whenever GSM network permits it. I'd very much like to set this up as
default during manufacturing. What configuration options do I have?
Connman version 1.36, ofono version 1.21 (debian buster).
So far I tried setting configuration option
"AutoConnectRoamingServices=true" in file "/etc/connman/main.conf" and
restarted connman and ofono, but this doesn't seem to have any effect.
Option RoamingAllowed remains "false" in ofono config
(/var/lib/ofono/248030010014875/gprs). It seems like connman does not
tell ofono to enable roaming, so it remains disabled. Is this
configuration option perhaps not supported in 1.36?
I can tell ofono to enable roaming manually - either via the config file
or dbus interface, but I'd prefer that connman does that automatically
whenever I provision a SIM card with "connmanctl connect cellular_xxx"
or setting up the /var/lib/connman/ configuration files.
As context: working on a 3G-equipped gateway device, factory-installed
with a roaming-enabled SIM card and typically shipped to a foreign
country (mostly within EU where data roaming incurs no penalty). It's
rather desirable that 3G comes online without requiring any setup
whatsoever once the gateway is powered on in destination country.
--
Kind regards
Tarmo Kuuse
------------------------------
Message: 2
Date: Tue, 23 Jul 2019 19:18:52 +0200
From: Nuno Gon?alves <[email protected]>
To: [email protected]
Subject: IP Pool collision resolution not working when two
technologies tethered
Message-ID:
<caexmxlqy5ev6kdhp0u71hnebbajuk_aj47q46ovp4je02ps...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
Connman assigns by default the DHCP pool 192.168.0.x to the tether interface.
If another interface comes online with a IP in this subnet, then
__connman_ippool_newaddr calls collision_cb() to restart the tether
interface so that it gets a chance to get a new pool.
Unfortunately if two technologies are tethered (WiFi and Gadget), then
this logic does not work. It fails at
__connman_tethering_set_disabled, since tethering_enabled == 2.
I really don't understand the big picture to offer a patch for this. I
guess it's not enough to just remove this check!
Thanks,
Nuno
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 45, Issue 15
***************************************
