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. miracast connections using connman disconnect after 30 mins
(DHCP renewal problem?) (Carl D. Blake)
2. Re: Using NTP To Set System Time (Jeff Gray)
3. AW: connmand[186]: Online check failed but running dhclient
manually fixes this issue (Eswaran Vinothkumar (BEG/PJ-IOT-EL))
----------------------------------------------------------------------
Message: 1
Date: Thu, 20 Jul 2017 15:22:14 -0700
From: "Carl D. Blake" <[email protected]>
To: [email protected]
Subject: miracast connections using connman disconnect after 30 mins
(DHCP renewal problem?)
Message-ID: <1500589334.26575.186.camel@ironhills>
Content-Type: text/plain; charset="UTF-8"
I've been using connman in an application involving doing miracast
connections. I've been using libwds and connman 1.34 as well as
wpa_supplicant V2.6.
I'm encountering a problem where I can establish a miracast connection
with an android device, but after 30 mins. the entire connection drops.
This is the messages I see when that happens:
---------------------------------------------
Jul 14 22:54:48 cr-400-2ac2 wpa_supplicant[945]: wlan0: Failed to
initiate sched scan
Jul 14 23:17:01 cr-400-2ac2 CRON[1523]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Jul 14 23:20:01 cr-400-2ac2 connmand[926]: Peer DHCP server: Received
REQUEST NIP 0
Jul 14 23:20:01 cr-400-2ac2 kernel: [ 1884.087547] DHCP - REQUEST [RX]
Jul 14 23:20:03 cr-400-2ac2 kernel: [ 1886.228326] DHCP - REQUEST [RX]
Jul 14 23:20:11 cr-400-2ac2 kernel: [ 1894.311831] DHCP - REQUEST [RX]
Jul 14 23:20:28 cr-400-2ac2 kernel: [ 1911.745592] DHCP - REQUEST [RX]
Jul 14 23:19:48 cr-400-2ac2 wpa_supplicant[945]: message repeated 5
times: [ wlan0: Failed to initiate sched scan]
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: p2p-wlan0-1:
AP-STA-DISCONNECTED b6:ef:39:39:5b:df p2p_dev_addr=b6:ef:39:39:db:df
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: AP-STA-DISCONNECTED
b6:ef:39:39:5b:df p2p_dev_addr=b6:ef:39:39:db:df
Jul 14 23:20:29 cr-400-2ac2 cpn: * Source unavailable
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: P2P-GROUP-REMOVED
p2p-wlan0-1 GO reason=REQUESTED
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: p2p-wlan0-1: interface
state ENABLED->DISABLED
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: p2p-wlan0-1:
AP-DISABLED
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: p2p-wlan0-1:
CTRL-EVENT-DISCONNECTED bssid=02:04:4b:58:aa:c0 reason=3
locally_generated=1
Jul 14 23:20:28 cr-400-2ac2 connmand[926]: message repeated 3 times:
[ Peer DHCP server: Received REQUEST NIP 0]
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {RX} 367084
packets 399923565 bytes
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {TX} 156 packets
19838 bytes
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {update} flags
102403 <UP,LOWER_UP>
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {newlink} index
10 address 02:04:4B:58:AA:C0 mtu 1500
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {newlink} index
10 operstate 5
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {update}
flags 102403 <UP,LOWER_UP>
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {newlink}
index 10 address 02:04:4B:58:AA:C0 mtu 1500
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {newlink}
index 10 operstate 5
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.126009] [07-14 23:20:29.280]
wl_notify_connect_status_ap: event WLC_E_DEAUTH_IND(6) status 0 reason 3
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.126039] [07-14 23:20:29.280]
wl_notify_connect_status_ap: event WLC_E_DISASSOC_IND(12) status 0
reason 8
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.128488]
wl_cfg80211_del_station : Disconnect STA : b6:ef:39:39:5b:df scb_val.val
3
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.132741]
wl_cfg80211_del_station : Disconnect STA : ff:ff:ff:ff:ff:ff scb_val.val
3
Jul 14 23:20:29 cr-400-2ac2 wpa_supplicant[945]: nl80211: deinit
ifname=p2p-wlan0-1 disabled_11b_rates=0
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {RX} 367084
packets 399923565 bytes
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {TX} 157 packets
19904 bytes
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {update} flags
102467 <UP,RUNNING,LOWER_UP>
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {newlink} index
10 address 02:04:4B:58:AA:C0 mtu 1500
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {newlink} index
10 operstate 6
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {update}
flags 102467 <UP,RUNNING,LOWER_UP>
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {newlink}
index 10 address 02:04:4B:58:AA:C0 mtu 1500
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {newlink}
index 10 operstate 6
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.251941]
dhd_cfg80211_clean_p2p_info : Clean : op_mode=0x0005
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.253235] 'cfg p2p_ifdis' error
-23
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {update}
flags 36866
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {newlink}
index 10 address 02:04:4B:58:AA:C0 mtu 1500
Jul 14 23:20:29 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {newlink}
index 10 operstate 2
Jul 14 23:20:29 cr-400-2ac2 avahi-daemon[471]: Interface
p2p-wlan0-1.IPv6 no longer relevant for mDNS.
Jul 14 23:20:29 cr-400-2ac2 avahi-daemon[471]: Leaving mDNS multicast
group on interface p2p-wlan0-1.IPv6 with address fe80::4:4bff:fe58:aac0.
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {update} flags
36866
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {newlink} index
10 address 02:04:4B:58:AA:C0 mtu 1500
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {newlink} index
10 operstate 2
Jul 14 23:20:29 cr-400-2ac2 avahi-daemon[471]: Interface
p2p-wlan0-1.IPv4 no longer relevant for mDNS.
Jul 14 23:20:29 cr-400-2ac2 avahi-daemon[471]: Leaving mDNS multicast
group on interface p2p-wlan0-1.IPv4 with address 192.168.0.1.
Jul 14 23:20:29 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {del} route
fe80:: gw :: scope 0
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.259164]
"dhd->iflist[*ifidx] != NULL": file "dhd_linux.c", line 8106
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.260405] deleting interface
'p2p-wlan0-1' idx 1
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.260429] dhd_get_stats: BAD_IF
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.260873] dhd_get_stats: BAD_IF
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.261266] dhd_get_stats: BAD_IF
Jul 14 23:20:29 cr-400-2ac2 kernel: [ 1912.261289]
wl_cfg80211_netdev_notifier_call : [NETDEV_DOWN] wait for complete of
cleanup_work (0 th)
Jul 14 23:20:30 cr-400-2ac2 connmand[926]: Inconsistent IP pool
management (start not found)
Jul 14 23:20:30 cr-400-2ac2 connmand[926]: (null) {del} address
192.168.0.1/24 label p2p-wlan0-1
Jul 14 23:20:30 cr-400-2ac2 kernel: [ 1913.255689] dhd_get_stats: BAD_IF
Jul 14 23:20:30 cr-400-2ac2 kernel: [ 1913.255817] Cannot find ifidx
for(p2p-wlan0-1) set to 0
Jul 14 23:20:30 cr-400-2ac2 kernel: [ 1913.263179] dhd_get_stats: BAD_IF
Jul 14 23:20:30 cr-400-2ac2 connmand[926]: p2p-wlan0-1 {dellink} index
10 operstate 2
Jul 14 23:20:30 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {dellink}
index 10 operstate 2
Jul 14 23:20:30 cr-400-2ac2 connman-vpnd[940]: p2p-wlan0-1 {remove}
index 10
Jul 14 23:20:30 cr-400-2ac2 connmand[926]: (null) {remove} index 10
Jul 14 23:20:30 cr-400-2ac2 avahi-daemon[471]: IP_DROP_MEMBERSHIP
failed: No such device
Jul 14 23:20:30 cr-400-2ac2 connmand[926]: Remove interface (null)
[ wifi ]
Jul 14 23:20:30 cr-400-2ac2 avahi-daemon[471]: Withdrawing address
record for fe80::4:4bff:fe58:aac0 on p2p-wlan0-1.
Jul 14 23:20:30 cr-400-2ac2 avahi-daemon[471]: Withdrawing address
record for 192.168.0.1 on p2p-wlan0-1.
Jul 14 23:20:30 cr-400-2ac2 avahi-daemon[471]: Withdrawing workstation
service for p2p-wlan0-1.
Jul 14 23:20:30 cr-400-2ac2 kernel: [ 1913.325494] dhd_get_stats: BAD_IF
Jul 14 23:20:30 cr-400-2ac2 kernel: [ 1913.325699] DHD-MON:
dhd_del_monitor IF not found in monitor array, is this a monitor IF?
0xffffffc0f4f2a800
Jul 14 23:20:30 cr-400-2ac2 kernel: [ 1913.326204] wl_dealloc_netinfo :
Unknown wdev freeed!
Jul 14 23:21:23 cr-400-2ac2 wpa_supplicant[945]: P2P-DEVICE-LOST
p2p_dev_addr=b6:ef:39:39:db:df
Jul 14 23:21:23 cr-400-2ac2 wpa_supplicant[945]: dbus: Unregister peer
object '/fi/w1/wpa_supplicant1/Interfaces/1/Peers/b6ef3939dbdf'
Jul 14 23:21:23 cr-400-2ac2 cpn: * Peer removed: SAMSUNG-SM-G360V
-----------------------------------------
I originally thought it had something to do with miracast and asked this
question at that site, but the people there thought it might be an issue
with connman.
It seems like there might be some issue with DHCP renewal. Does anybody
know what's happening here?
------------------------------
Message: 2
Date: Fri, 21 Jul 2017 13:21:15 +1000
From: Jeff Gray <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: Using NTP To Set System Time
Message-ID:
<CAHb0zt=s5ND2nWgnFLmzfisLaiRniD9K6Brai0xjP=bnuvv...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
On 21 July 2017 at 04:14, Daniel Wagner <[email protected]> wrote:
> That is a huge jump. Unfortunately, I don't have setup a timeserver
> here so I can't verify it.
The embedded system has no real time clock, so it boots with 1-1-1998.
> I just checked the code and ConnMan uses adjtimex() with ADJ_SETOFFSET
> and followed them into the kernel. In kernel/time/ntp.c I see that
> the range is checked if it is valid:
That helps me narrow in on where to look.
> adjtimex() should do the work, suppose we use it correctly. I have seen
> it in the past work. So it might be that the kernel is not accepting
> the values. Are their any message in the kernel log?
No kernel log messages
I enabled debugging in ntp.c and get this result:
connmand[433]: src/ntp.c:decode_msg() flags : 0x1c
connmand[433]: src/ntp.c:decode_msg() stratum : 3
connmand[433]: src/ntp.c:decode_msg() poll : 1024.000000 seconds (10)
connmand[433]: src/ntp.c:decode_msg() precision : 0.015625 seconds (-6)
connmand[433]: src/ntp.c:decode_msg() root delay : 0 seconds (fraction 26128)
connmand[433]: src/ntp.c:decode_msg() root disp. : 0 seconds (fraction 58128)
connmand[433]: src/ntp.c:decode_msg() reference : 0xd61a9278
connmand[433]: src/ntp.c:decode_msg() requested version 4, accepting version 3
connmand[433]: src/ntp.c:decode_msg() org=3092601676.059537
rec=3709592087.130712 xmt=3709592087.130712 dst=3092601676.143208
connmand[433]: src/ntp.c:decode_msg() offset=616990411.029340 delay=0.083671
connmand[433]: src/ntp.c:decode_msg() Timeserver 10.16.1.4, next sync
in 1024 seconds
connmand[433]: ntp: adjust (jump): +616990411.029340 sec
connmand[433]: src/ntp.c:decode_msg() interval/delta/delay/drift
1024.000000s/+616990411.029s/0.084s/+0ppm
Everything looks OK, and since we see the final debug message and
don't see "Failed to adjust time", this means that adjtimex didn't
return an error.
I installed the ntpd client in Busybox & tested that since it uses
adjtimex as well. It successfully sets the system time.
ntpd -d -n -p 10.16.1.4
ntpd: sending query to 10.16.1.4
ntpd: reply from 10.16.1.4: offset:+616990410.993984 delay:0.002816
status:0x1c strat:3 refid:0xd61a9278 rootdelay:0.064057 reach:0x01
ntpd: sending query to 10.16.1.4
ntpd: reply from 10.16.1.4: offset:+616990410.994545 delay:0.002000
status:0x1c strat:3 refid:0xd61a9278 rootdelay:0.064057 reach:0x03
ntpd: setting time to 2017-07-21 02:15:51.347783 (offset +616990410.994545s)
Looking at the output, they are quite similar, so it is a mystery why
it would not be working in connman. I have to consider that if ntp is
working for others in connman, it might be something unusual about my
embedded system. It is running an old 2.6.33 kernel, so maybe there is
a subtle incompatibility.
------------------------------
Message: 3
Date: Fri, 21 Jul 2017 05:53:24 +0000
From: "Eswaran Vinothkumar (BEG/PJ-IOT-EL)"
<[email protected]>
To: Daniel Wagner <[email protected]>, "[email protected]"
<[email protected]>
Subject: AW: connmand[186]: Online check failed but running dhclient
manually fixes this issue
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hallo Daniel,
Thanks for your reply.
Hi Vinothkumar,
On 07/17/2017 04:39 PM, Eswaran Vinothkumar (BEG/PJ-IOT-EL) wrote:
> Hello,
>
> I am trying to use connman+ofono to connect to internet using TELIT
> 910 EUG modem chip.
>
> Versions Used: Connman:1.34 and Ofono:1.20
>
> To establish the internet connection I am using the python scripts
> within the ofono/test directory as follows:
>
> /usr/lib/ofono/test/enable-modem
>
> /usr/lib/ofono/test/online-modem
>
> /usr/lib/ofono/test/set-roaming-allowed
>
> /usr/lib/ofono/test/register-auto
>
> /usr/lib/ofono/test/enable-gprs
>
> /usr/lib/ofono/test/create-internet-context web.vodafone.de vodafone
> vodafone
>
> /activate-context
>
> /process-context-settings
>
> After this I could see that the device gets the IP address, gateway
> and nameserver as shown below,
>
> ofono_start_gsm.sh[192]: Interface is wwan0
>
> ofono_start_gsm.sh[192]: IP address is 10.249.29.20
>
> ofono_start_gsm.sh[192]: Gateway is 10.249.29.21
>
> ofono_start_gsm.sh[192]: Nameserver is 10.105.144.254
>
> At this point I excepted Connman to connect to the internet but it doesn't.
Indeed, now it should be online. What does ConnMan say about the service:
./test/list-services
The service is in ready state.
connmanctl services
*AR Vodafone cellular_204046850339628_context1
*AR Wired ethernet_0001c01df20b_cable
?
> I am seeing the following error message from Connman, >
> connmand[186]: Online check failed for 0x50db78 Vodafone.
If the routes would be setup correctly I assume this online check would also
work. So we get the routing somehow wrong.
> From the debug message I understood that connman is not able to connect to
> the internet(status 400).
Yes, there is a section on the online check in the README.
> But if I run manually dhclient on wwan0 interface, I could connect to
> the internet. It puzzles me, why it is not working with connman. Any
> help on this topic would be great J
Sure, glad to help. Just a bit limited bandwidth on my side. If you could post
the logs of oFono and ConnMan we maybe identify what is going wrong. At least
we can compare what dhclient is doing.
I have attached the logs for your reference. Debug messages for both ConnMan
and oFono are enabled (-d).
Thanks,
Vinoth
Thanks,
Danie.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: connman_telit_vodafone_log.txt
URL:
<http://lists.01.org/pipermail/connman/attachments/20170721/4b85fa40/attachment.txt>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 21, Issue 10
***************************************
