Hi Jiajia,

> I ran tests on the latest ConnMan code. 
> I have some questions about the results of "list-networks". Please find the 
> questions marked with ****** below.
>  
>  [ /dev_00_13_E8_05_7E_7D ]
>     [ /dev_00_13_E8_05_7E_7D/otc__________asus_ven ]
>         Available = 1
> ******** What are the available values for "Available"? 

if details are unclear, then we have to improve network-api.txt do give
a clear documentation on what these properties many.

So Available means it is found during the last scan. This is different
to known networks that might be in the list from previous attempts. So
if you mark a network as Remember then it will show up here. The
Available then means that it is in range.

>         Strength = 43
> ******** What is the available range for "Strength"? Is it related with 
> "Signal level" or "Link Quality" in the outputs of command "iwconfig"?

It is currently normalized to out of 100 and in fact translates to the
quality value from WEXT. I am checking if we better use 100 or 255 as
normalization value. Neverless it is a made-up and most not present
physical values from the hardware.

Since this value would be used for WiMAX and WiFi, I have to check what
it the best method first. That needs some research.

>         WiFi.Passphrase = 1111000000
> ******** I don't understand here. The passphrase for WiFi network should be 
> hidden, isn't it? Everyone knowing the Passphrase for a wireless network is 
> violating its security. While another AP listed below--" jane_asus" has 
> "WiFi.Passphrase =" and " WiFi.Security = wep". I think it is the right 
> behavior.

This code path is not finished yet. We do wanna have the support for
reading passphrases back from the storage. We will protect it with
PolicyKit and then it is up the integrators do define a security policy.

However these are all pre-shared keys and so their security strength is
questionable anyway.

>         Remember = 0
> ******** Is "Remember" expected to be set to "1" after the network is 
> connected? I never saw it changed. 

You can connect to a network and not remember it. You have to set this
property manually. If Remember is set, ConnMan will auto-reconnect to
this network. Otherwise it won't.

We do have to give the UI the choice here.

>         WiFi.Security = none
> ******** Why "Security" is "none" here? Given " WiFi.Passphrase = 
> 1111000000", "Security" should be "wep", right?

The Security value is derived from the scan results and the scan result
said that you AP is not using WEP. This might be a bug of course, but
with all my access points this worked perfectly fine.

>         Connected = 0
>         WiFi.SSID = [ otc-11215947-asus-ven ]

Crap. My invalid character replacement routine is broken. Number are
perfectly fine D-Bus path characters and I replace them :(

>         Policy = auto
>         Name = otc-11215947-asus-ven
> ******* Sometimes, I saw one AP is listed twice or more. Is it a bug?

That is a bug and I have seen that one too. It must be race condition in
the scanning code. However so far I haven't found a way to reproduce it
reliable. It happens randomly.

Regards

Marcel


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

Reply via email to