Hidden SSID

[Daniel (Youngwhan) Song]

Hi,

I updated connman 0.78 to 0.79, and it looks the previous ConnectService() API has removed.

I'm trying to figure out how I can associate hidden ssid via connman 0.79.

1. The scan list doesn't show all hidden ssids. While looking at "http://connman.net/blogs/patrik/2012/connman-079", it is saying that "There will be one hidden service created per WiFi security method should one appear in the scan".

However, I feel it doesn't make sense. What if several routers using hidden ssids are being used in home?

2. It is hard to interpret how the agent-api works. I tried to test simple-agent python script, but I don't know how I can achieve to associate the hidden ssid via the agent.

Can anyone help me how I can access hidden ssids properly? The main problem to me is that the hidden ssids what I'm looking for are not shown in service lists. (I saw a few, but they are not what I'm looking for. I set the hidden ssid with WPA security, but no service name shows any "psk" at the end of the service name. I could see _wep, _none, _ieee8021x, though.)


Best Regards,
Daniel (Youngwhan) Song
***@gmail.com

[Patrik Flykt]

Hi,

Post by Daniel (Youngwhan) Song
1. The scan list doesn't show all hidden ssids. While looking at
"http://connman.net/blogs/patrik/2012/connman-079", it is saying that
"There will be one hidden service created per WiFi security method
should one appear in the scan".
However, I feel it doesn't make sense. What if several routers using
hidden ssids are being used in home?

There will be a hidden service created for each of the security types,
i.e. one each for none, WEP, WPA and 802.11. When the user tries to
connect to one of these, the Agent API will request for a 'Name' or
'SSID' to be returned in addition to the passphrase. The user can thus
fill in the required SSID for the network. In the next scan, the same
(or another) access point will still be hidden, so the hidden network
entry will still show up.

Post by Daniel (Youngwhan) Song
2. It is hard to interpret how the agent-api works. I tried to test
simple-agent python script, but I don't know how I can achieve to
associate the hidden ssid via the agent.

To the simple-agent 'Answer: ' prompt reply with the string
'Name=yourssidhere' in addition to the passphrase, e.g.: 'Name=MyWiFi
Passphrase=foobar'. The documentation is unfortunately the python source
code...

Post by Daniel (Youngwhan) Song
shown in service lists. (I saw a few, but they are not what I'm
looking for. I set the hidden ssid with WPA security, but no service
name shows any "psk" at the end of the service name. I could see _wep,
_none, _ieee8021x, though.)

That's too bad. For some reason the WPA access point did not show up in
the scan. Try scanning again and check that the access point actually is
in WPA mode.


Cheers,

Patrik

[Daniel (Youngwhan) Song]

Thank you so much for the nice explanation, Patrick.

Post by Patrik Flykt

Post by Daniel (Youngwhan) Song
shown in service lists. (I saw a few, but they are not what I'm
looking for. I set the hidden ssid with WPA security, but no service
name shows any "psk" at the end of the service name. I could see _wep,
_none, _ieee8021x, though.)

That's too bad. For some reason the WPA access point did not show up in
the scan. Try scanning again and check that the access point actually is
in WPA mode.

It is WPA mode indeed, but still I don't see the hidden_psk yet. However, if I tried to connect _ieee8021x, it connects. Is it ok to use _ieee8021x instead of waiting for _psk? From the experiment, it looks it works, though, but I am not sure if it is right or not.


Best Regards,
Daniel (Youngwhan) Song
***@gmail.com

[Patrik Flykt]

Post by Daniel (Youngwhan) Song
However, if I tried to connect _ieee8021x, it connects. Is it ok to
use _ieee8021x instead of waiting for _psk?

I don't think this is correct. With a _ieee8021x other code paths in
ConnMan are taken, I don't know how you would get it working in the
first place.

Cheers,

Patrik