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. Support LTE and WiFi network switch (JH)
2. Re: Support LTE and WiFi network switch (Daniel Wagner)
3. RE: Support LTE and WiFi network switch
(Eswaran Vinothkumar (BEG/PJ-IOT-D))
4. Re: Support LTE and WiFi network switch (Daniel Wagner)
5. Re: [PATCH] Fix faulty error handling in inet.c (Daniel Wagner)
6. Re: [Patch][gsupplicant]Added support for auth type "ttls"
abd phase 2 value "GTC" incase of 802.1x Security for Peap
(Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Feb 2019 11:01:17 +1100
From: JH <[email protected]>
To: [email protected]
Subject: Support LTE and WiFi network switch
Message-ID:
<CAA=hcWSpeAMuoQww_in1AG=cnagnzpcevhxim+r--cfvw7z...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
Sorry for asking basic questions, I am new to connman and the list,
but it seems to me that connman targets to the embedded system, a
perfect light weight network management library for the embedded
system. I am using ublox SARA LTE Cat M1 / NB1 module, EMMY-W1 WiFi
and BLE in a tiny Linux embedded system running on C / C++
applications, has anyone known if there are drivers that connman can
support those modules? Anything I need be aware of before using the
connman?
I also need network switching capability, the LTE is the default
network interface, when the system detects WiFi is available, it
switches from LTE to WiFi network connection immediately which is
similar to the mobile phone to automatically switch from LTE to the
WiFi. I think the connman must has that capacity as well, but correct
me if I am wrong.
The dbus is a desktop bus as the name implies, is it mandatory that
connman has to use dbus? I heard there are problems for embedded
system to use dbus, but please correct me.
Are there any preference of Linux distribution that will be the best
for running connman? I have been thinking to use either Debian armhf
or OpenWrt, appreciate your comments.
Thank you.
Kind regards,
jupiter
------------------------------
Message: 2
Date: Tue, 19 Feb 2019 09:10:39 +0100
From: Daniel Wagner <[email protected]>
To: JH <[email protected]>
Cc: [email protected]
Subject: Re: Support LTE and WiFi network switch
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
On 19.02.19 01:01, JH wrote:
> Sorry for asking basic questions, I am new to connman and the list,
> but it seems to me that connman targets to the embedded system, a
> perfect light weight network management library for the embedded
> system. I am using ublox SARA LTE Cat M1 / NB1 module, EMMY-W1 WiFi
> and BLE in a tiny Linux embedded system running on C / C++
> applications, has anyone known if there are drivers that connman can
> support those modules? Anything I need be aware of before using the
> connman?
ConnMan doesn't support GSM/LTE modems directly. Instead it is using
oFono for handling all the low level interaction with modems. The same
is with Bluetooth. For this ConnMan uses BlueZ. For WiFi ConnMan is able
to stear wpa_supplicant, or iwd. Though iwd plugin needs some updates
(e.g. scaning support and tethering). In short, ConnMan does configure
and maintain networking interfaces, the 'hardware' drivers are part of
external projects.
> I also need network switching capability, the LTE is the default
> network interface, when the system detects WiFi is available, it
> switches from LTE to WiFi network connection immediately which is
> similar to the mobile phone to automatically switch from LTE to the
> WiFi. I think the connman must has that capacity as well, but correct
> me if I am wrong.
Yes, that is what ConnMan is doing. Though this depends on how good the
hardware and the drivers work.
> The dbus is a desktop bus as the name implies, is it mandatory that
> connman has to use dbus? I heard there are problems for embedded
> system to use dbus, but please correct me.
D-Bus is mandatory. I am not sure what problems you are referring. It is
possible to use also in embedded system. These days you can use a
completety new reimplementation of the D-Bus daemon which is should work
way better (read resource usage)
https://bus1.org/
https://github.com/bus1/dbus-broker
"""
The core of dbus-broker (the `dbus-broker` binary) has no external
dependencies at all, other than a linux kernel. It is a complete bus
implementation according to the dbus specification (see `dbus-broker(1)`
man-page).
"""
> Are there any preference of Linux distribution that will be the best
> for running connman? I have been thinking to use either Debian armhf
> or OpenWrt, appreciate your comments.
Any distro which brings the right dependencies with it works fine.
Debian armhf will work without any problems (doing this myself). I
suppose OpenWrt works but I don't know it by fact.
Thanks,
Daniel
------------------------------
Message: 3
Date: Tue, 19 Feb 2019 17:28:08 +0000
From: "Eswaran Vinothkumar (BEG/PJ-IOT-D)"
<[email protected]>
To: Daniel Wagner <[email protected]>, JH <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: RE: Support LTE and WiFi network switch
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi,
On 19.02.19 01:01, JH wrote:
> Sorry for asking basic questions, I am new to connman and the list,
> but it seems to me that connman targets to the embedded system, a
> perfect light weight network management library for the embedded
> system. I am using ublox SARA LTE Cat M1 / NB1 module, EMMY-W1 WiFi
> and BLE in a tiny Linux embedded system running on C / C++
> applications, has anyone known if there are drivers that connman can
> support those modules? Anything I need be aware of before using the
> connman?
ConnMan doesn't support GSM/LTE modems directly. Instead it is using oFono for
handling all the low level interaction with modems. The same is with Bluetooth.
For this ConnMan uses BlueZ. For WiFi ConnMan is able to stear wpa_supplicant,
or iwd. Though iwd plugin needs some updates (e.g. scaning support and
tethering). In short, ConnMan does configure and maintain networking
interfaces, the 'hardware' drivers are part of external projects.
> I also need network switching capability, the LTE is the default
> network interface, when the system detects WiFi is available, it
> switches from LTE to WiFi network connection immediately which is
> similar to the mobile phone to automatically switch from LTE to the
> WiFi. I think the connman must has that capacity as well, but correct
> me if I am wrong.
Yes, that is what ConnMan is doing. Though this depends on how good the
hardware and the drivers work.
Hi Daniel,
Please correct me if I am wrong. The switch between LTE and Wifi is not
automatic and immediate as like in mobile phone. For example, during the
system startup if I have only cellular connectivity, Connman uses this
interface(provided by ofono) for data connection. If after sometime, wifi
network is available, Connman add this interface(provided by bluez) but in
ready state and not in online state. This still means that the data connection
is still through cellular network. Connman doesn't change to wifi network just
because it's available. The switch to wifi happens, if the cellular
communication breaks completely or a manual interruption using connmanctl
disconnect cellular_* and connmanctl connect wlan_*
Thanks & Regards,
Vinothkumar
> The dbus is a desktop bus as the name implies, is it mandatory that
> connman has to use dbus? I heard there are problems for embedded
> system to use dbus, but please correct me.
D-Bus is mandatory. I am not sure what problems you are referring. It is
possible to use also in embedded system. These days you can use a completety
new reimplementation of the D-Bus daemon which is should work way better (read
resource usage)
https://bus1.org/
https://github.com/bus1/dbus-broker
"""
The core of dbus-broker (the `dbus-broker` binary) has no external dependencies
at all, other than a linux kernel. It is a complete bus implementation
according to the dbus specification (see `dbus-broker(1)` man-page).
"""
> Are there any preference of Linux distribution that will be the best
> for running connman? I have been thinking to use either Debian armhf
> or OpenWrt, appreciate your comments.
Any distro which brings the right dependencies with it works fine.
Debian armhf will work without any problems (doing this myself). I suppose
OpenWrt works but I don't know it by fact.
Thanks,
Daniel
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
Message: 4
Date: Tue, 19 Feb 2019 19:53:25 +0100
From: Daniel Wagner <[email protected]>
To: "Eswaran Vinothkumar (BEG/PJ-IOT-D)"
<[email protected]>
Cc: JH <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: Support LTE and WiFi network switch
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
>>> I also need network switching capability, the LTE is the default
>>> network interface, when the system detects WiFi is available, it
>>> switches from LTE to WiFi network connection immediately which is
>>> similar to the mobile phone to automatically switch from LTE to the
>>> WiFi. I think the connman must has that capacity as well, but correct
>>> me if I am wrong.
>>
>> Yes, that is what ConnMan is doing. Though this depends on how good
>> the hardware and the drivers work.
>>
> Please correct me if I am wrong. The switch between LTE and Wifi is
> not automatic and immediate as like in mobile phone. For example,
> during the system startup if I have only cellular connectivity,
> Connman uses this interface(provided by ofono) for data
> connection. If after sometime, wifi network is available, Connman
> add this interface(provided by bluez) but in ready state and not in
> online state. This still means that the data connection is still
> through cellular network. Connman doesn't change to wifi network
> just because it's available. The switch to wifi happens, if the
> cellular communication breaks completely or a manual interruption
> using connmanctl disconnect cellular_* and connmanctl connect
> wlan_*
The auto connect algorithm can be tweaked via a set of configuration
option. Furhtermore, you can even implement your own connection
algorithm via the plugin interface.
Check the connman.conf page for all the config options, in particular
SingleConnectedTechnology.
Note the online check (ready -> online state) is only executed
once. None limitation.
------------------------------
Message: 5
Date: Tue, 19 Feb 2019 20:17:11 +0100
From: Daniel Wagner <[email protected]>
To: Matthias Berndt <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] Fix faulty error handling in inet.c
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Matthias
On Mon, Feb 18, 2019 at 12:56:57AM +0100, Matthias Berndt wrote:
> I was recently trying to run connman on postmarketOS, and it crashed while
> setting up the routes for the wifi connection. I ran it again in gdb and
> while I couldn't get a full stacktrace, I did see that it crashes because it
> passes a NULL pointer to freeaddrinfo.
>
> So I took a look at the source code and went through all the calls to that
> function in connman. There aren't that many, and they all have error
> handling code to prevent this - except for one. The attached patch should
> fix it.
Great catch. Patch applied after adding a bit more explenation to the
commit message.
Thanks,
Daniel
------------------------------
Message: 6
Date: Tue, 19 Feb 2019 20:29:01 +0100
From: Daniel Wagner <[email protected]>
To: Rahul Jain <[email protected]>
Cc: "[email protected]" <[email protected]>, AMIT KUMAR JAISWAL
<[email protected]>, Bhaskar Dutta <[email protected]>
Subject: Re: [Patch][gsupplicant]Added support for auth type "ttls"
abd phase 2 value "GTC" incase of 802.1x Security for Peap
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Rahul,
On Mon, Feb 18, 2019 at 05:54:17PM +0530, Rahul Jain wrote:
> Dear Daniel,
>
> From: Rahul Jain <[email protected]>
> Date: Mon, 18 Feb 2019 17:53:16 +0530
> Subject: [PATCH] [Patch][gsupplicant]Added support for auth type ttls abd
> phase 2 value GTC incase of 802.1x Security for Peap
>
> Signed-off-by: Rahul Jain <[email protected]>
We don't do the SoB.
Patch applied.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 40, Issue 9
**************************************
