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)
----------------------------------------------------------------------
Message: 1
Date: Sun, 11 Aug 2019 21:57:01 +1000
From: JH <[email protected]>
To: Giacinto Cifelli <[email protected]>
Cc: connman <[email protected]>, ofono <[email protected]>
Subject: Re: Unsalble cellular connection
Message-ID:
<CAA=hcWSK7P6DP=pjCg7pdUDC=Cz9=pnwj7_u02zjrw8u8ug...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
More observation about the network connection, the device has two
network interfaces, WiFi mlan0 and LTE wwan0, I think that problem is
likely in connman, not in ofono as in some stage, the wifi IP address
lost as well, but it came back.
Why connmand contently calling to add and to del both mlan0 and wwan0
in route table? How does the connman manage the route, dhcp to refresh
interface IP address?
Aug 11 08:01:43 connmand[204]: mlan0 {add} route 0.0.0.0 gw
192.168.0.1 scope 0 <UNIVERSE>
Aug 11 08:01:44 connmand[204]: wwan0 {del} route 212.227.81.55 gw
10.116.108.45 scope 0 <UNIVERSE>
Aug 11 08:01:44 connmand[204]: mlan0 {del} route 0.0.0.0 gw
192.168.0.1 scope 0 <UNIVERSE>
Aug 11 08:01:44 connmand[204]: wwan0 {add} route 0.0.0.0 gw
10.116.108.45 scope 0 <UNIVERSE>
Aug 11 08:01:44 connmand[204]: wwan0 {add} route 212.227.81.55 gw
10.116.108.45 scope 0 <UNIVERSE>
Aug 11 08:01:45 connmand[204]: wwan0 {del} route 212.227.81.55 gw
10.116.108.45 scope 0 <UNIVERSE>
Aug 11 08:02:48 connmand[204]: wwan0 {RX} 1365 packets 142181 bytes
Aug 11 08:02:49 connmand[204]: wwan0 {TX} 1672 packets 221297 bytes
Aug 11 08:02:49 connmand[204]: wwan0 {update} flags 4240 <DOWN>
Aug 11 08:02:49 connmand[204]: wwan0 {newlink} index 4 address
00:00:00:00:00:00 mtu 1500
Aug 11 08:02:49 connmand[204]: wwan0 {newlink} index 4 operstate 2 <DOWN>
Aug 11 08:02:49 connmand[204]: (null) {del} address 10.116.108.44/29 label wwan0
Aug 11 08:02:49 connmand[204]: wwan0 {dellink} index 4 operstate 2 <DOWN>
Aug 11 08:02:49 connmand[204]: (null) {RX} 1365 packets 142181 bytes
Aug 11 08:02:49 connmand[204]: (null) {TX} 1672 packets 221297 bytes
Aug 11 08:02:49 connmand[204]: (null) {remove} index 4
Aug 11 08:02:49 connmand[204]: Remove interface (null) [ cellular ]
Aug 11 08:02:49 connmand[204]: Removing default gateway route failed
(No such device)
Thank you.
Kind regards,
- jh
On 8/9/19, JH <[email protected]> wrote:
> Hi Giacinto,
>
> I tried to run openwrt on my embedded system, it got netifd daemon to
> manage the LTE modem, and started udhcpc -p /var/run/udhcpc-wwan0.pid
> -s /lib/netifd, that problem has gone away.
>
> Now I am really worried, if the problem of lost LTE network IP address
> only happened in connman not in openwrt, it will unlikely be the carry
> network and modem issues, could it be because that openwrt used udhcpc
> to refresh the IP address? How does the connman manage the dhcp for
> LTE IP address?
>
> Thank you.
>
> Kind regards,
>
> - jh
>
> On 8/9/19, Giacinto Cifelli <[email protected]> wrote:
>>> > Ask uBlox how to capture a protocol stack trace, and if it is feasible
>>> > for your application, do it and have it analyzed by uBlox.
>>> >
>>> > Are you on GSM, on LTE catM or on LTE NB-IOT when this happens? On
>>> > which network operator and country?
>>>
>>> It is LTE Cat-M1, the operator is Telstra in Australia. I will be very
>>> interested in finding out what is going on.
>>
>> you need stack traces.
>> Most likely the chipset you are using is the MDM9205, so the trace will
>> be
>> QXDM.
>>
>>>
>>> Thank you.
>>>
>>> Kind regards,
>>>
>>> - jupiter
>>
>> BR,
>> Giacinto
>>
>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 46, Issue 7
**************************************
