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. Tether WiFi to cellular modem uplink (Evade Flow)
2. Re: Connman v1.33 with systemd v230 : experiencing delay in
IP assignment (Shrikant Bobade)
----------------------------------------------------------------------
Message: 1
Date: Thu, 8 Dec 2016 18:00:37 -0500
From: Evade Flow <[email protected]>
To: [email protected]
Subject: Tether WiFi to cellular modem uplink
Message-ID:
<camab8zm2y_1qttkqyz-eysufgx0r3-t0eatjabnmq9opior...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm trying set up an embedded Linux device as a WiFi hotspot. Clients
connect via WiFi, and the uplink to the Internet is via either Ethernet or,
more recently, cellular modem. The device uses connmand version 1.30 and
ofonod version 1.17. When I started on the project, the only uplink
connection available was via wired Ethernet, and it has been working well.
I've been tasked with adding the ability to tether to the cellular uplink,
and that... isn't working quite so well. `:-]
I guess I should start by confessing that I was completely mystified by
ofono, so I gave up trying to use it to configure the modem connection.
Instead, I wrote some udev rules that do (more-or-less) the following:
ip link set eth0 down
qmi-cli -p -d /dev/cdc-wdm0 --wda-set-data-format=802-3
qmicli -p -d /dev/cdc-wdm0 --wds-start-network=apn=fast.t-mobile.com
--client-no-release-cid
killall -TERM dhclient
dhclient wwan0
ip link set eth0 up
This 'works' in the sense that the routing table is correct afterwards, and
a user logged in to the embedded device is able to ping machines on both
the wired LAN and the Internet. From the perspective of the embedded
device, everything is fine.
Unfortunately, when I enable tethering using:
embedded-dev $ connmanctl tether wifi enable
Enabled tethering for wifi
and then connect to the hotspot from another machine, things don't work as
I'd hoped; the bridge *looks* the same as it does for the Ethernet uplink:
embedded-dev $ brctl show
bridge name bridge id STP enabled interfaces
tether 8000.98f1706fcbb3 no mlan0
But on the client machine, I see this:
client-dev $ ping google.com
ping: unknown host google.com
client-dev $ ping 8.8.8.8
<hangs forever>
I also noticed that DNS lookups on the client for machines on the (wired)
LAN work fine:
client-dev $ nslookup reverie.acme.com
Server: 192.168.1.1
Address: 192.168.1.1#53
Name: reverie.acme.com
Address: 10.222.150.207
but DNS lookups for machines on the Internet fail:
client-dev $ nslookup google.com
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find google.com: NXDOMAIN
I suspect this is because connman knows *nothing* about the cellular
connection:
$ # These commands were run back on the embedded device:
$ connmanctl technologies
/net/connman/technology/p2p
Name = P2P
Type = p2p
Powered = False
Connected = False
Tethering = False
TetheringAt5ghz = False
/net/connman/technology/bluetooth
Name = Bluetooth
Type = bluetooth
Powered = True
Connected = False
Tethering = False
TetheringAt5ghz = False
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = True
TetheringIdentifier = myapn
TetheringPassphrase = myapnpasswd
TetheringAt5ghz = False
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = True
Connected = True
Tethering = False
TetheringAt5ghz = False
Can anyone tell me what I need to do to allow clients to connect to the
Internet via the embedded device's cellular connection. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20161208/e97a3ad1/attachment-0001.html>
------------------------------
Message: 2
Date: Fri, 9 Dec 2016 19:07:21 +0530
From: Shrikant Bobade <[email protected]>
To: Patrik Flykt <[email protected]>
Cc: [email protected]
Subject: Re: Connman v1.33 with systemd v230 : experiencing delay in
IP assignment
Message-ID:
<CALwQErqTR=g-A01d+QPzF=V1Rktn-4FF562DoTYZZ1hKCT=d...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Daniel & Patrik,
Thanks for the responses.
Checked with connman incrementally from v1.30 to v1.33, found out the delay
behaviour almost similar on my setup.
Also ensured systemd-networkd is not running on my setup.
Further observed with less available entropy.. on the setup causing the
delay. So continuing with v1.33.
e.g.
*:~# cat
/proc/sys/kernel/random/entropy_avail
0*
Getting connman waiting/stuck at
*getrandom (_rnd_get_system_entropy_getrandom) (by default gnutls enabled)*
So tried to increase entropy with help of /dev/urandom & and with
sufficient ~3k+ entropy count observed the getrandom call completed
successfully.
Is this know behaviour Or experienced by anyone.. ?
:~# rngd -r /dev/urandom -o
/dev/random
:~# cat /proc/sys/kernel/random/entropy_avail
3087
Please advise, we suppose to use only /dev/random for better security
reasons and not /dev/urandom ? thoughts if any for other ways to deal with
less/no entropy available with /dev/random?
http://security.stackexchange.com/questions/122155/how-bad-it-is-to-feed-dev-random-with-dev-urandom
http://stackoverflow.com/questions/3690273/did-i-understand-dev-urandom#comment30985465_3709644
Any pointers or references will be a great help..
Thanks
Shrikant
On Wed, Dec 7, 2016 at 7:27 PM, Patrik Flykt <[email protected]>
wrote:
> On Fri, 2016-11-25 at 15:38 +0530, Shrikant Bobade wrote:
> > Hi,
> >
> > I am using connman v1.33 along with systemd v230 for yocto based
> > project.
> > Experiencing delay in IP assignment ranging from 20 sec. to 1.5 min.
> >
> > While used earlier versions previously didn't faced such delays. So
> > by the time I am finding the exact change in version causing this
> > delay issue. Just want to check anyone experiencing such delays in IP
> > assignments.
> >
> > Any suggestions or pointers will be a great help.
>
> Ensure that you don't have systemd-networkd running, at least not on
> the interfaces used by ConnMan?
>
> Cheers,
>
> Patrik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20161209/26ed4926/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 14, Issue 15
***************************************
