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. Re: Unsalble cellular connection (JH)
   2. Waking from sleep, don't re-associate  (Christo Labuschagne)


----------------------------------------------------------------------

Message: 1
Date: Tue, 13 Aug 2019 08:09:03 +1000
From: JH <[email protected]>
To: Giacinto Cifelli <[email protected]>
Cc: connman <[email protected]>, ofono <[email protected]>,  Jonas
        Bonn <[email protected]>
Subject: Re: Unsalble cellular connection
Message-ID:
        <CAA=hcwqfvyg_hqhdf--vu2l-kn6z9nou_vb93eeewoaw7op...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Hi Jonas,

Do you have any comments about it?

Thank you.

Kind regards,

- jupiter

On 8/12/19, JH <[email protected]> wrote:
> Hi Giacinto,
>
> On 8/11/19, Giacinto Cifelli <[email protected]> wrote:
>
>> can you check with the ofono script test/list-contexts if the method
>> is static or dhcp?
>
> # ofono/test/list-contexts
> [ /ubloxqmi_0 ]
>     [ /ubloxqmi_0/context1 ]
>         Name = Internet
>         Type = internet
>         AuthenticationMethod = chap
>         Settings = { Method=static Gateway=10.116.103.22
> Netmask=255.255.255.25}
>         Username =
>         AccessPointName = telstra.m2m
>         Password =
>         Protocol = ip
>         IPv6.Settings = { }
>         Active = 1
>
> Looks like it is static, how can change it to a correct one (dynamic
>>)? Or any workarounds?
>
>> I believe this can be the problem: if ofono managed to get an IP
>> address, likely with at+cgpaddr and/or at+cgcontrdp,
>> then it passes it to connman, and then it is set on the interface...
>> static, with no lease expiration.
>
> There are two devices for the SARA-R4 modem, /dev/ttyUSB0 is used for
> QMI which is currently using as default protocol. /dev/ttyUSB1 is for
> AT, let me know if you like to check AT command, I have never tried to
> write / read AT command, are the following commands correct?
>
> echo "at+cgpaddr" > /dev/ttyUSB1
> cat < /dev/ttyUSB1
>
> Thank you very much Giacinto.
>
> -- jupiter
>


------------------------------

Message: 2
Date: Tue, 13 Aug 2019 07:00:46 +0000
From: Christo Labuschagne <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Waking from sleep, don't re-associate 
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Good day.

We are using connman (1.37) on embedded linux (4.17) mobile platform with 
wpa_supplicant (2.6) even tried with IWD (0.19).  As it is a battery powered 
device, we would like to be asleep as much as possible.  We would wake with an 
RTC timer to re-register on the server, but every time we wake, connman 
restarts the wifi connection which then takes the connection down, then up, 
then get new DHCP ip address.  Is this how something like android or iOS would 
do it when trying to maintain a push notification connection?  This process 
takes at least 5 seconds of valuable battery time every time I wake.

If I set up the connection from the command line and then assume we are 
connected in our application, we can wake, register and sleep again within less 
than 2 seconds, but then we are not relying on connman to handle the 
connection, which is then pointless.

Some more info on the setup:

*         We are listening on dbus.

*         Waking and sleeping via wakelocks.

*         Sleeping to s2idle state at this stage, but will be going to deeper 
state later.

*         With iw we set wowlan pattern to wake us when a message from server 
comes in.

*         For current testing we are stationary and waking every 30s.

Kind regards

Christo Labuschagne



Important Notice:

This e-mail and its contents are subject to the Nanoteq (Pty) Ltd e-mail legal 
notice available at:
http://www.nanoteq.com/AboutUs/EmailDisclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20190813/da6e03f4/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 46, Issue 9
**************************************

Reply via email to