8:02 a.m.
Hi,
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?
Thank you.
Kind regards,
- jupiter
6:56 p.m.
Hi!
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.
--
Kind regards,
Tarmo
8:22 a.m.
Hi,
On 4/21/19 7:56 PM, Tarmo Kuuse wrote:
Hi!
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.
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?
Best Regards,
Christophe Ronco
8:14 a.m.
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
12:13 p.m.
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
6:41 a.m.
Hi Daniel,
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.
What is your recommendation to fix the WiFi and Cellular autoconnect?
The autoconnect is not working, either we are missing something here
in configuration, or it could be bugs?
Thank you.
Kind regards,
- jupiter
7:25 a.m.
Hi JH,
On 4/25/19 7:41 AM, JH wrote:
What is your recommendation to fix the WiFi and Cellular
autoconnect?
The autoconnect is not working, either we are missing something here
in configuration, or it could be bugs?
I don't think I can't remember your scenario correctly. So you build a
rootfs which is deployed on embedded boars, right? The device is
supposed to connect either to WiFi or if that is not available to
Cellular? For WiFi and Cellular there are provisioning information
available upfront (user name, password, etc)?
Come to think of it, I am not 100% sure if this works currently without
code changes. It's one of many different use patterns I haven't really
tested so far. Given that you are not the first one asking for this kind
of setup I should try to setup something like this and figure out what
is not working. More for my todo list...
Obviously, this doesn't help you too much right now. Let me answer your
other mail. At least there is something you could try out.
Thanks,
Daniel
7:51 a.m.
Hi Daniel,
On 4/25/19, Daniel Wagner <wagi(a)monom.org> wrote:
Hi JH,
On 4/25/19 7:41 AM, JH wrote:
> What is your recommendation to fix the WiFi and Cellular autoconnect?
> The autoconnect is not working, either we are missing something here
> in configuration, or it could be bugs?
I don't think I can't remember your scenario correctly. So you build a
rootfs which is deployed on embedded boars, right? The device is
supposed to connect either to WiFi or if that is not available to
Cellular? For WiFi and Cellular there are provisioning information
available upfront (user name, password, etc)?
Correct, I defined PreferredTechnologies = wifi,cellular in main.conf
to connect to wifi first, if wifi is not available to connect to
cellular running on imx6 EVK.
Come to think of it, I am not 100% sure if this works currently
without
code changes. It's one of many different use patterns I haven't really
tested so far. Given that you are not the first one asking for this kind
of setup I should try to setup something like this and figure out what
is not working. More for my todo list...
Basically the auto connect does not work. At first time boot up, the
connman does not perform auto connect, I tried to deploy both wifi
(with SSID and Passphrase) and cellular settings to /var/lib/connman,
the connman still could not detect the wifi and cellular until I
perform manual configuration via connmanctl.
Obviously, this doesn't help you too much right now. Let me
answer your
other mail. At least there is something you could try out.
Unfortunately, I am still learning the connman, cannot make effective
contributions as I like to, but let me know if I can assist for
testing and debugging.
Thank you Daniel,
Kind regards,
- jupiter
7:56 a.m.
On 4/25/19 8:51 AM, JH wrote:
On 4/25/19, Daniel Wagner <wagi(a)monom.org> wrote:
Correct, I defined PreferredTechnologies = wifi,cellular in main.conf
to connect to wifi first, if wifi is not available to connect to
cellular running on imx6 EVK.
IIRC, there are some products which got this working with ConnMan. So
not all hope is lost.
Basically the auto connect does not work. At first time boot up, the
connman does not perform auto connect, I tried to deploy both wifi
(with SSID and Passphrase) and cellular settings to /var/lib/connman,
the connman still could not detect the wifi and cellular until I
perform manual configuration via connmanctl.
In the other mail you mentioned this. Though looking at the paths/file
names it looked wrong. The provisioning files life just under
/var/lib/connman and not in /var/lib/connman/$id/settings. Only files
under /var/lib/connman/$name.config will be monitored by ConnMan.
Thanks,
Daniel
8:32 a.m.
On 25.04.19 09:56, Daniel Wagner wrote:
> Basically the auto connect does not work. At first time boot up,
the
> connman does not perform auto connect, I tried to deploy both wifi
> (with SSID and Passphrase) and cellular settings to /var/lib/connman,
> the connman still could not detect the wifi and cellular until I
> perform manual configuration via connmanctl.
In the other mail you mentioned this. Though looking at the paths/file
names it looked wrong. The provisioning files life just under
/var/lib/connman and not in /var/lib/connman/$id/settings. Only files
under /var/lib/connman/$name.config will be monitored by ConnMan.
Where would I look to understand these provisioning files? The
"main.conf" is nicely documented by the Debian manpages, but the stuff
in "/var/lib/connman" is not. I'd settle for reading code, just need a
hint of where to start.
--
Kind regards
Tarmo
9:28 a.m.
Hi Daniel,
In the other mail you mentioned this. Though looking at the
paths/file
names it looked wrong. The provisioning files life just under
/var/lib/connman and not in /var/lib/connman/$id/settings. Only files
under /var/lib/connman/$name.config will be monitored by ConnMan.
I did try to use the $name.config, it did not work either, did I get
wrong with the $name?
$ cat /var/lib/connman/tpg-mcnf.conf
[service_wifi]
Name=TPG-MCNF
SSID=5450472d4d434e44
Passphrase=xxxxxx
AutoConnect=true
$ cat /var/lib/connman/telstra.conf
[cellular_505013520350165_context1]
Name=Telstra
Favorite=true
AutoConnect=true
Tarmo: You can find format and information in doc/config-format.txt.
Thank you.
- jupiter
9:56 a.m.
Sorry, type the wrong config file name, it is tpg-mcnf.config and
telstra.config, tried to change both to wifi.config and
celluar.config, no avail either.
On 4/25/19, JH <jupiter.hce(a)gmail.com> wrote:
Hi Daniel,
> In the other mail you mentioned this. Though looking at the paths/file
> names it looked wrong. The provisioning files life just under
> /var/lib/connman and not in /var/lib/connman/$id/settings. Only files
> under /var/lib/connman/$name.config will be monitored by ConnMan.
I did try to use the $name.config, it did not work either, did I get
wrong with the $name?
$ cat /var/lib/connman/tpg-mcnf.conf
[service_wifi]
Name=TPG-MCNF
SSID=5450472d4d434e44
Passphrase=xxxxxx
AutoConnect=true
$ cat /var/lib/connman/telstra.conf
[cellular_505013520350165_context1]
Name=Telstra
Favorite=true
AutoConnect=true
Tarmo: You can find format and information in doc/config-format.txt.
Thank you.
- jupiter
9:17 a.m.
Hi Jupiter,
On 25.04.19 11:28, JH wrote:
I did try to use the $name.config, it did not work either, did I get
wrong with the $name?
$ cat /var/lib/connman/tpg-mcnf.conf
[service_wifi]
Name=TPG-MCNF
SSID=5450472d4d434e44
Passphrase=xxxxxx
AutoConnect=true
$ cat /var/lib/connman/telstra.conf
[cellular_505013520350165_context1]
Name=Telstra
Favorite=true
AutoConnect=true
Tarmo: You can find format and information in doc/config-format.txt.
Thanks!
BTW: you've used ".conf" suffix but the document mandates
".config".
Regardless, connman v1.36 certainly doesn't follow the file structure
described in doc/config-format.txt. After manually provisioning my
dial-up connection I can see directories:
/var/lib/connman/cellular_248030054743345_context1/
/var/lib/connman/ethernet_00e04c2154c3_cable/
Both contain two files "data" and "settings". Here's a
"settings" file,
which does what you're looking to do - start the dial-up on boot.
--- begin ---
[cellular_248030054743345_context1]
Name=Tele2 EE
Favorite=true
AutoConnect=true
Modified=2019-04-22T12:57:30.161163Z
IPv4.method=fixed
IPv4.netmask_prefixlen=32
IPv4.local_address=[...snip...]
IPv6.method=off
IPv6.privacy=disabled
--- end ---
The "data" file contains some garbage which I don't recognize.
Anyway, the service name and configuration format revolve around the
IMSI of the SIM card. Does this mean that I can only pre-provision a
cellular service if I know in advance the IMSI of the SIM card to be used?
--
Kind regards
Tarmo
11:08 a.m.
Hi Tarmo,
BTW: you've used ".conf" suffix but the document
mandates ".config".
Yeap, I sent another email to correct my typo.
Regardless, connman v1.36 certainly doesn't follow the file
structure
described in doc/config-format.txt. After manually provisioning my
dial-up connection I can see directories:
/var/lib/connman/cellular_248030054743345_context1/
/var/lib/connman/ethernet_00e04c2154c3_cable/
Both contain two files "data" and "settings". Here's a
"settings" file,
which does what you're looking to do - start the dial-up on boot.
That is the normal connman set up, I think what Daniel and document
said was if you deploy a file ${name}.config to /var/lib/connman, the
connman daemon will be notified and auto connect those services
without manual configuration that what embedded systems require. But
the auto connect feature does not seem work, Daniel is busy.
Daniel, if you could let me know that is the issue to cause auto
connect not working, where to look, I will try it.
Thank you.
Kind regards,
- jupiter
8:28 p.m.
On 4/26/19 12:08 PM, JH wrote:
> BTW: you've used ".conf" suffix but the document
mandates ".config".
Yeap, I sent another email to correct my typo.
You can see what ConnMan thinks of your config file by
# ./connmand -n -d src/config.c
connmand[11316]: Adding configuration test
connmand[11316]: Type of the configured service is missing for group
service_home
connmand[11316]: Config file /var/lib/connman/test.config does not
contain any configuration that can be provisioned!
connmand[11316]: Removing configuration .#test
connmand[11316]: Adding configuration .#test
connmand[11316]: Removing configuration test
connmand[11316]: Adding configuration test
connmand[11316]: Type of the configured service is missing for group
service_home
> Regardless, connman v1.36 certainly doesn't follow the file
structure
> described in doc/config-format.txt. After manually provisioning my
> dial-up connection I can see directories:
>
> /var/lib/connman/cellular_248030054743345_context1/
> /var/lib/connman/ethernet_00e04c2154c3_cable/
>
> Both contain two files "data" and "settings". Here's a
"settings" file,
> which does what you're looking to do - start the dial-up on boot.
That is the normal connman set up, I think what Daniel and document
said was if you deploy a file ${name}.config to /var/lib/connman, the
connman daemon will be notified and auto connect those services
without manual configuration that what embedded systems require. But
the auto connect feature does not seem work, Daniel is busy.
Daniel, if you could let me know that is the issue to cause auto
connect not working, where to look, I will try it.
I understand you have at least two problems which you try to solve. For
the provisioning the above trick might help.
Can you post the output from the list-services script?
Thanks,
Daniel
11:35 p.m.
Hi Daniel,
On 4/30/19, Daniel Wagner <wagi(a)monom.org> wrote:
On 4/26/19 12:08 PM, JH wrote:
>> BTW: you've used ".conf" suffix but the document mandates
".config".
>
> Yeap, I sent another email to correct my typo.
You can see what ConnMan thinks of your config file by
# ./connmand -n -d src/config.c
Thanks for the debug tip, here was the result:
# connmand -n -d src/config.c
connmand[316]: Connection Manager version 1.35
connmand[316]: Adding configuration wifi
connmand[316]: Unknown configuration key AutoConnect in [service_wifi]
connmand[316]: Config file /var/lib/connman/wifi.config does not
contain any configuration that can be provisioned!
connmand[316]: Adding configuration cellular
connmand[316]: Config file /var/lib/connman/cellular.config does not
contain any configuration that can be provisioned!
connmand[316]: Adding configuration telstra
connmand[316]: Config file /var/lib/connman/telstra.config does not
contain any configuration that can be provisioned!
connmand[316]: Adding configuration tpg-mcnf
connmand[316]: Unknown configuration key AutoConnect in [service_wifi]
connmand[316]: Config file /var/lib/connman/tpg-mcnf.config does not
contain any configuration that can be provisioned!
connmand[316]: Checking loopback interface settings
connmand[316]: System hostname is solarevk
connmand[316]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
connmand[316]: lo {newlink} index 1 operstate 0 <UNKNOWN>
connmand[316]: eth0 {create} index 2 type 1 <ETHER>
connmand[316]: eth0 {RX} 1366 packets 1565375 bytes
connmand[316]: eth0 {TX} 537 packets 56096 bytes
connmand[316]: eth0 {update} flags 36866 <DOWN>
connmand[316]: eth0 {newlink} index 2 address 00:04:9F:05:0F:C0 mtu 1500
connmand[316]: eth0 {newlink} index 2 operstate [ 526.743775] Micrel
KSZ8081 or KSZ8091 20b4000.ethernet-1:01: attached PHY driver [Micrel
KSZ8081 or KSZ8091] (mii_bus:phy_addr=20b4000.ethernet-1:01, irq=POLL)
2 <DOWN>
connmand[316]: Adding interface eth0 [ ethernet ]
connmand[316]: eth1 {create} index 3 type 1 <ETHER>
connmand[316]: eth1 {update} flags 36866 <DOWN>
connmand[316]: eth1 {newlink} index 3 address 00:04:9F:05:0F:BF mtu 1500
connmand[316]: eth1 {newlink} index 3 operstate 2 <DOWN>
[ 526.839872] Micrel KSZ8081 or KSZ8091 20b4000.ethernet-1:02:
attached PHY driver [Micrel KSZ8081 or KSZ8091]
(mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
connmand[316]: Adding interface eth1 [ ethernet ]
connmand[316]: sit0 {newlink} index 4 address 00:00:00:00:08:00 mtu 1480
connmand[316]: sit0 {newlink} index 4 operstate 2 <DOWN>
connmand[316]: can0 {newlink} index 5 address 00:00:00:00:00:00 mtu 16
connmand[316]: can0 {newlink} index 5 operstate 2 <DOWN>
connmand[316]: eth0 {RX} 1366 packets 1565375 bytes
connmand[316]: eth0 {TX} 537 packets 56096 bytes
connmand[316]: eth0 {update} flags 36867 <UP>
connmand[316]: eth0 {newlink} index 2 address 00:04:9F:05:0F:C0 mtu 1500
connmand[316]: eth0 {newlink} index 2 operstate 2 <DOWN>
connmand[316]: can1 {newlink} index 6 address 00:00:00:00:00:00 mtu 16
connmand[316]: can1 {newlink} index 6 operstate 2 <DOWN>
connmand[316]: mlan0 {create} index 7 type 1 <ETHER>
connmand[316]: mlan0 {update} flags 4098 <DOWN>
connmand[316]: mlan0 {newlink} index 7 address D4:CA:6E:00:1B:C0 mtu 1500
connmand[316]: mlan0 {newlink} index 7 operstate 2 <DOWN>
connmand[316]: Adding interface mlan0 [ wifi ]
connmand[316]: eth1 {update} flags 36867 <UP>
connmand[316]: eth1 {newlink} index 3 address 00:04:9F:05:0F:BF mtu 1500
connmand[316]: eth1 {newlink} index 3 operstate 2 <DOWN>
[ 528.866542] fec 20b4000.ethernet eth0: Link is Up - 100Mbps/Full -
flow control rx/tx
[ 528.875057] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
connmand[316]: eth0 {add} route ff00:: gw :: scope 0 <UNIVERSE>
connmand[316]: eth0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
connmand[316]: eth0 {RX} 1366 packets 1565375 bytes
connmand[316]: eth0 {TX} 537 packets 56096 bytes
connmand[316]: eth0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
connmand[316]: eth0 {newlink} index 2 address 00:04:9F:05:0F:C0 mtu 1500
connmand[316]: eth0 {newlink} index 2 operstate 6 <UP>
connmand[316]: Skipping disconnect of carrier, network is connecting.
connmand[316]: eth0 {add} address 192.168.1.13/24 label eth0 family 2
connmand[316]: eth0 {add} route 192.168.1.0 gw 0.0.0.0 scope 253 <LINK>
connmand[316]: eth0 {add} route 192.168.1.1 gw 0.0.0.0 scope 253 <LINK>
connmand[316]: eth0 {add} route 0.0.0.0 gw 192.168.1.1 scope 0 <UNIVERSE>
connmand[316]: eth0 {add} route 212.227.81.55 gw 192.168.1.1 scope 0 <UNIVERSE>
connmand[316]: eth0 {add} route fd50:4b8:60c3:600:: gw :: scope 0 <UNIVERSE>
connmand[316]: eth0 {del} route 212.227.81.55 gw 192.168.1.1 scope 0 <UNIVERSE>
connmand[316]: eth0 {add} address
fd50:4b8:60c3:600:204:9fff:fe05:fc0/64 label (null) family 10
Hmm, looks like the configure file is not proper formatted, I
referenced the configure file format from config-format.txt, would was
I missing?
# cat wifi.config
[global]
Name = wifi
Description = WiFi
[service_wifi]
Name=TPG-MCNF
SSID=5450472d4d434e46
Passphrase=XXXXX
AutoConnect=true
# cat cellular.config
[global]
Name = cellular
Description = Cellular
[service_cellular]
Name=Telstra
Favorite=true
AutoConnect=true
I understand you have at least two problems which you try to solve.
For
the provisioning the above trick might help.
Can you post the output from the list-services script?
That script was not built in image, I'll have to add the test script
to the image and post the output here soon.
Thank you Daniel.
- jupiter
7:51 a.m.
On 4/30/19 12:35 AM, JH wrote:
Hmm, looks like the configure file is not proper formatted, I
referenced the configure file format from config-format.txt, would was
I missing?
# cat wifi.config
[global]
Name = wifi
Description = WiFi
[service_wifi]
Name=TPG-MCNF
SSID=5450472d4d434e46
Passphrase=XXXXX
AutoConnect=true
# cat cellular.config
[global]
Name = cellular
Description = Cellular
[service_cellular]
Name=Telstra
Favorite=true
AutoConnect=true
Type is missing. See examples in config-format.txt
9:39 a.m.
Hi Daniel,
Type is missing. See examples in config-format.txt
OK, fixed all errors, both wifi and cellular services are added, but
the WiFi and cellular are still not shown in network interface at
follows:
# connmand -n -d src/config.c
connmand[360]: Connection Manager version 1.35
connmand[360]: Adding configuration wifi
connmand[360]: Adding service configuration wifi
connmand[360]: Adding configuration cellular
connmand[360]: Adding service configuration cellular
connmand[360]: Checking loopback interface settings
connmand[360]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
connmand[360]: lo {newlink} index 1 operstate 0 <UNKNOWN>
<DOWN>
connmand[360]: Adding interface eth0 [ ethernet ]
[ 1318.264479] Micrel KSZ8081 or KSZ8091 20b4000.ethernet-1:02:
attached PHY driver [Micrel KSZ8081 or KSZ8091]
(mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
connmand[360]: Adding interface eth1 [ ethernet ]
connmand[360]: sit0 {newlink} index 4 address 00:00:00:00:08:00 mtu 1480
connmand[360]: sit0 {newlink} index 4 operstate 2 <DOWN>
connmand[360]: wwan0 {create} index 5 type 1 <ETHER>
connmand[360]: wwan0 {update} flags 4098 <DOWN>
connmand[360]: wwan0 {newlink} index 5 address AE:9E:88:64:6F:1B mtu 1500
connmand[360]: wwan0 {newlink} index 5 operstate 2 <DOWN>
connmand[360]: Adding interface wwan0 [ cellular ]
connmand[360]: mlan0 {create} index 8 type 1 <ETHER>
connmand[360]: mlan0 {update} flags 36866 <DOWN>
connmand[360]: mlan0 {newlink} index 8 address D4:CA:6E:60:D7:F9 mtu 1500
connmand[360]: mlan0 {newlink} index 8 operstate 2 <DOWN>
connmand[360]: Adding interface mlan0 [ wifi ]
I removed Ethernet cable just in case, no wifi and cellular:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:9F:05:0F:C0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31217 (30.4 KiB) TX bytes:43427 (42.4 KiB)
eth1 Link encap:Ethernet HWaddr 00:04:9F:05:0F:BF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8392 (8.1 KiB) TX bytes:8392 (8.1 KiB)
Anything I could still be missing here?
Thank you.
- jupiter
6:29 a.m.
Hi Daniel,
Both wifi.config and cellular.config are able to be added by connman,
but I have to run command line manually "connmanctl enable cellular"
and "connmanctl enable wifi" to bring both online. Are there any
key-value in config file for automatically enable\ing the interfaces
without calling "connmanctl enable cellular / wifi" manually? I
checked the config-format.txt, but could not find anything.
Thank you.
Kind regards,
- jupiter
On 4/30/19, JH <jupiter.hce(a)gmail.com> wrote:
Hi Daniel,
> Type is missing. See examples in config-format.txt
OK, fixed all errors, both wifi and cellular services are added, but
the WiFi and cellular are still not shown in network interface at
follows:
# connmand -n -d src/config.c
connmand[360]: Connection Manager version 1.35
connmand[360]: Adding configuration wifi
connmand[360]: Adding service configuration wifi
connmand[360]: Adding configuration cellular
connmand[360]: Adding service configuration cellular
connmand[360]: Checking loopback interface settings
connmand[360]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
connmand[360]: lo {newlink} index 1 operstate 0 <UNKNOWN>
<DOWN>
connmand[360]: Adding interface eth0 [ ethernet ]
[ 1318.264479] Micrel KSZ8081 or KSZ8091 20b4000.ethernet-1:02:
attached PHY driver [Micrel KSZ8081 or KSZ8091]
(mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
connmand[360]: Adding interface eth1 [ ethernet ]
connmand[360]: sit0 {newlink} index 4 address 00:00:00:00:08:00 mtu 1480
connmand[360]: sit0 {newlink} index 4 operstate 2 <DOWN>
connmand[360]: wwan0 {create} index 5 type 1 <ETHER>
connmand[360]: wwan0 {update} flags 4098 <DOWN>
connmand[360]: wwan0 {newlink} index 5 address AE:9E:88:64:6F:1B mtu 1500
connmand[360]: wwan0 {newlink} index 5 operstate 2 <DOWN>
connmand[360]: Adding interface wwan0 [ cellular ]
connmand[360]: mlan0 {create} index 8 type 1 <ETHER>
connmand[360]: mlan0 {update} flags 36866 <DOWN>
connmand[360]: mlan0 {newlink} index 8 address D4:CA:6E:60:D7:F9 mtu 1500
connmand[360]: mlan0 {newlink} index 8 operstate 2 <DOWN>
connmand[360]: Adding interface mlan0 [ wifi ]
I removed Ethernet cable just in case, no wifi and cellular:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:9F:05:0F:C0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31217 (30.4 KiB) TX bytes:43427 (42.4 KiB)
eth1 Link encap:Ethernet HWaddr 00:04:9F:05:0F:BF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8392 (8.1 KiB) TX bytes:8392 (8.1 KiB)
Anything I could still be missing here?
Thank you.
- jupiter
7:01 a.m.
Hi JH,
On Thu, May 02, 2019 at 03:29:57PM +1000, JH wrote:
Both wifi.config and cellular.config are able to be added by
connman,
but I have to run command line manually "connmanctl enable cellular"
and "connmanctl enable wifi" to bring both online. Are there any
key-value in config file for automatically enable\ing the interfaces
without calling "connmanctl enable cellular / wifi" manually? I
checked the config-format.txt, but could not find anything.
The default settings for the technology enabled/disabled is in the
/var/lib/connman/settings file. Try to deploy something like
below. Note ConnMan should not run when you add or edit the file.
# cat /var/lib/connman/settings
[global]
OfflineMode=false
[Wired]
Enable=true
Tethering=false
[WiFi]
Enable=true
12:37 p.m.
Thank you very much Daniel, that did the trick.
Kind regards,
- jupiter
On 5/2/19, Daniel Wagner <wagi(a)monom.org> wrote:
Hi JH,
On Thu, May 02, 2019 at 03:29:57PM +1000, JH wrote:
> Both wifi.config and cellular.config are able to be added by connman,
> but I have to run command line manually "connmanctl enable cellular"
> and "connmanctl enable wifi" to bring both online. Are there any
> key-value in config file for automatically enable\ing the interfaces
> without calling "connmanctl enable cellular / wifi" manually? I
> checked the config-format.txt, but could not find anything.
The default settings for the technology enabled/disabled is in the
/var/lib/connman/settings file. Try to deploy something like
below. Note ConnMan should not run when you add or edit the file.
# cat /var/lib/connman/settings
[global]
OfflineMode=false
[Wired]
Enable=true
Tethering=false
[WiFi]
Enable=true
8:24 p.m.
On 4/25/19 10:28 AM, JH wrote:
Hi Daniel,
> In the other mail you mentioned this. Though looking at the paths/file
> names it looked wrong. The provisioning files life just under
> /var/lib/connman and not in /var/lib/connman/$id/settings. Only files
> under /var/lib/connman/$name.config will be monitored by ConnMan.
I did try to use the $name.config, it did not work either, did I get
wrong with the $name?
$ cat /var/lib/connman/tpg-mcnf.conf
[service_wifi]
Name=TPG-MCNF
SSID=5450472d4d434e44
Passphrase=xxxxxx
AutoConnect=true
$ cat /var/lib/connman/telstra.conf
[cellular_505013520350165_context1]
Name=Telstra
Favorite=true
AutoConnect=true
Tarmo: You can find format and information in doc/config-format.txt.
Did you try to add 'Type="?
9:57 a.m.
New subject: Why can't connman automatically enable and connect to cellular
network interface?
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 <wagi(a)monom.org> 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
> connman(a)lists.01.org
> https://lists.01.org/mailman/listinfo/connman
>
8:15 a.m.
New subject: Why can't connman automatically enable and connect to cellular
network interface?
Hi JH,
On Mon, Jan 06, 2020 at 08:57:04PM +1100, JH wrote:
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?
autoconnect is a policy. I don't want to hardcode this, because for
some users, they want autoconnect out of the box, while others
don't. So far the approach we have in ConnMan is only do something
when we have an user telling us to do it.
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.
I'm sorry, I don't understand what you are saying.
Why can't connman and ofono automatically connecting to cellular
network
based on SIM and network registration?
As I said, it's not impossible but rather a policy thing. I am not
against getting things sorted out that autoconnect works. But don't
expect me to do it.
Thanks,
Daniel
862
days inactive
1123
days old
23 comments
4 participants
participants (4)
-
Christophe Ronco -
Daniel Wagner -
JH -
Tarmo Kuuse