Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe 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. Zeus failed DHCP (JH)
2. Re: Wifi Signal Strength (Daniel Wagner)
3. Re: Wifi Signal Strength (chaitanya cherukuri)
----------------------------------------------------------------------
Date: Wed, 19 Feb 2020 21:36:50 +1100
From: JH <[email protected]>
Subject: Zeus failed DHCP
To: Patches and discussions about the oe-core layer
<[email protected]>
Cc: Yocto discussion list <[email protected]>, connman
<[email protected]>
Message-ID:
<CAA=hcWSt-bNt=FVNX0hi-bhvgxrN2rrYLai1m2Upk2=pkzk...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi,
My build connman on Thud works on WiFi, but Zeus does not work, the
connman could not get WiFi DHCP response, it puts a local IP address
169.254.24.188 to my WiFi interface. Has anyone found that the problem
in Zeus or it just me may be miss some packages or configuration?
What are packages could cause DHCP not working?
Here is Thud working log:
# systemctl status connman -l
��● connman.service - Connection service
Loaded: loaded
(8;;file://solar/lib/systemd/system/connman.service/lib/systemd/system/connman.service8;;;
enabl)
Active: active (running) since Thu 2020-02-13 03:18:51 UTC; 6 days ago
Main PID: 131 (connmand)
CGroup: /system.slice/connman.service
��└��─131 /usr/sbin/connmand -n
Feb 18 22:37:16 solar connmand[131]: rp_filter set to 2 (loose mode
routing), old value was 1
Feb 18 22:37:16 solar connmand[131]: mlan0 {add} address
192.168.0.100/24 label mlan0 family 2
Feb 18 22:37:16 solar connmand[131]: mlan0 {add} route 192.168.0.0 gw
0.0.0.0 scope 253 <LINK>
Feb 18 22:37:16 solar connmand[131]: mlan0 {add} route 192.168.0.1 gw
0.0.0.0 scope 253 <LINK>
Feb 18 22:37:16 solar connmand[131]: mlan0 {add} route 212.227.81.55
gw 192.168.0.1 scope 0 <UNIVERSE>
Feb 18 22:37:17 solar connmand[131]: mlan0 {del} route 212.227.81.55
gw 192.168.0.1 scope 0 <UNIVERSE>
Feb 18 22:37:17 solar connmand[131]: wwan0 {del} route 0.0.0.0 gw
10.114.57.126 scope 0 <UNIVERSE>
Feb 18 22:37:17 solar connmand[131]: mlan0 {add} route 0.0.0.0 gw
192.168.0.1 scope 0 <UNIVERSE>
Feb 18 22:37:17 solar connmand[131]: mlan0 {add} route 212.227.81.55
gw 192.168.0.1 scope 0 <UNIVERSE>
Feb 18 22:37:17 solar connmand[131]: mlan0 {del} route 212.227.81.55
gw 192.168.0.1 scope 0 <UNIVERSE>
# systemctl status wpa_supplicant -l
��● wpa_supplicant.service - WPA supplicant
Loaded: loaded
(8;;file://solar/lib/systemd/system/wpa_supplicant.service/lib/systemd/system/wpa_supplicant.service8;;;
disabled; vendor preset: enabled)
Active: active (running) since Thu 2020-02-13 03:18:53 UTC; 6 days ago
Main PID: 503 (wpa_supplicant)
CGroup: /system.slice/wpa_supplicant.service
��└��─503 /usr/sbin/wpa_supplicant -u
Feb 19 07:37:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 07:47:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 07:57:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 08:07:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 08:17:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 08:19:01 solar wpa_supplicant[503]: mlan0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-85 noise=-97 txrate=1000
Feb 19 08:27:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 08:37:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 08:47:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Feb 19 08:57:29 solar wpa_supplicant[503]: mlan0: WPA: Group rekeying
completed with 34:08:04:12:b1:a2 [GTK=TKIP]
Here is Zenu build did not work:
# systemctl status connman -l
* connman.service - Connection service
Loaded: loaded
(8;;file://solar/lib/systemd/system/connman.service/lib/systemd/system/connman.service8;;;
enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-02-18 00:47:43 UTC; 1 day 9h ago
Main PID: 184 (connmand)
CGroup: /system.slice/connman.service
`-184 /usr/sbin/connmand -n
Feb 19 10:27:33 solar connmand[184]: mlan0 {newlink} index 3 operstate
5 <DORMANT>
Feb 19 10:27:33 solar connmand[184]: mlan0 {add} route ff00:: gw ::
scope 0 <UNIVERSE>
Feb 19 10:27:33 solar connmand[184]: mlan0 {add} route fe80:: gw ::
scope 0 <UNIVERSE>
Feb 19 10:27:33 solar connmand[184]: mlan0 {RX} 10 packets 1650 bytes
Feb 19 10:27:33 solar connmand[184]: mlan0 {TX} 256 packets 96668 bytes
Feb 19 10:27:33 solar connmand[184]: mlan0 {update} flags 102467
<UP,RUNNING,LOWER_UP>
Feb 19 10:27:33 solar connmand[184]: mlan0 {newlink} index 3 address
D4:CA:6E:9A:7E:29 mtu 1500
Feb 19 10:27:33 solar connmand[184]: mlan0 {newlink} index 3 operstate 6 <UP>
Feb 19 10:28:13 solar connmand[184]: mlan0 {add} address
169.254.241.106/16 label mlan0 family 2
Feb 19 10:28:14 solar connmand[184]: mlan0 {add} route 169.254.0.0 gw
0.0.0.0 scope 253 <LINK>
# systemctl status wpa_supplicant -l
* wpa_supplicant.service - WPA supplicant
Loaded: loaded
(8;;file://solar/lib/systemd/system/wpa_supplicant.service/lib/systemd/system/wpa_supplicant.service8;;;
disabled; vendor preset: disabled)
Active: active (running) since Tue 2020-02-18 00:47:48 UTC; 1 day 9h ago
Main PID: 263 (wpa_supplicant)
CGroup: /system.slice/wpa_supplicant.service
`-263 /usr/sbin/wpa_supplicant -u
Feb 19 09:57:33 solar wpa_supplicant[263]: mlan0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-47 noise=-92 txrate=65000
Feb 19 10:05:36 solar wpa_supplicant[263]: mlan0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-52 noise=-92 txrate=72200
Feb 19 10:07:32 solar wpa_supplicant[263]: mlan0:
CTRL-EVENT-DISCONNECTED bssid=34:08:04:12:b1:a2 reason=2
Feb 19 10:07:32 solar wpa_supplicant[263]: dbus:
wpa_dbus_property_changed: no property SessionLength in object
/fi/w1/wpa_supplicant1/Interfaces/0
Feb 19 10:07:33 solar wpa_supplicant[263]: mlan0: Trying to associate
with 34:08:04:12:b1:a2 (SSID='Jupiter' freq=2437 MHz)
Feb 19 10:07:33 solar wpa_supplicant[263]: mlan0: Associated with
34:08:04:12:b1:a2
Feb 19 10:07:33 solar wpa_supplicant[263]: mlan0:
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb 19 10:07:33 solar wpa_supplicant[263]: mlan0: WPA: Key negotiation
completed with 34:08:04:12:b1:a2 [PTK=CCMP GTK=TKIP]
Feb 19 10:07:33 solar wpa_supplicant[263]: mlan0: CTRL-EVENT-CONNECTED
- Connection to 34:08:04:12:b1:a2 completed [id=0 id_str=]
Feb 19 10:07:33 solar wpa_supplicant[263]: mlan0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-51 noise=-92 txrate=65000
Thank
------------------------------
Date: Wed, 19 Feb 2020 12:00:53 +0100
From: Daniel Wagner <[email protected]>
Subject: Re: Wifi Signal Strength
To: chaitanya cherukuri <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi,
On Tue, Feb 18, 2020 at 09:15:12PM -0500, chaitanya cherukuri wrote:
> I'm newbie to connman, so please excuse me for silly questions.
> Could someone explain how to make sense of the wifi signal strength
> number? I have a service which is reporting 67 as signal strength.
> what does this mean? Almost all my services are reporting around
> 65-69. Does this mean the signal quality is good?
Signal strength range is between 0 to 100. ConnMan just maps the
values reported by either iwd or wpa_supplicant. E.g. the range for
iwd is -10000 to 0.
So if the values are not what you expect, you need to look at the
firmware/driver/wpa_supplicant layer.
Thanks,
Daniel
------------------------------
Date: Wed, 19 Feb 2020 07:31:53 -0500
From: chaitanya cherukuri <[email protected]>
Subject: Re: Wifi Signal Strength
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Message-ID:
<calvd-wopkepckkzrqkjc2z8m-hsjpr4ygwaami7-ff7bdhz...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
On Wed, Feb 19, 2020 at 6:00 AM Daniel Wagner <[email protected]> wrote:
>
> Hi,
>
> On Tue, Feb 18, 2020 at 09:15:12PM -0500, chaitanya cherukuri wrote:
> > I'm newbie to connman, so please excuse me for silly questions.
> > Could someone explain how to make sense of the wifi signal strength
> > number? I have a service which is reporting 67 as signal strength.
> > what does this mean? Almost all my services are reporting around
> > 65-69. Does this mean the signal quality is good?
>
> Signal strength range is between 0 to 100. ConnMan just maps the
> values reported by either iwd or wpa_supplicant. E.g. the range for
> iwd is -10000 to 0.
>
> So if the values are not what you expect, you need to look at the
> firmware/driver/wpa_supplicant layer.
>
In plugins/wifi.c, the function calculate_strength returns the maximum
value of 100 or 120+
g_supplicant_network_get_signal(supplicant_network)
so signal greater than -20 will report the strength of 100, can I
consider that particular signal strength as 100%?
one other question, wifi security is reported as PSK. How do I know
the encryption method?
> Thanks,
> Daniel
Thanks,
Chaitanya
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 52, Issue 20
***************************************
