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. Connect to any access point which has WPS activated
(Robert Tiemann)
----------------------------------------------------------------------
Message: 1
Date: Wed, 10 Jan 2018 11:08:40 +0100
From: Robert Tiemann <[email protected]>
To: [email protected]
Subject: Connect to any access point which has WPS activated
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
I am trying to get WPS working. It works for simple cases, but I am
struggling with getting it right in case there are several access
points in reach.
What I am trying to achieve is to connect automatically to *any*
access point which has WPS activated (push button method), and use the
agent API to accept any connection. The target network should not have
to be preselected by the user. It would be very nice if ConnMan would
offer such functionality over D-Bus, but I could not find anything
like this.
As far as I can see, what I have to do instead is to check all wifi
services for WPS capabilities (net.connman.Manager.GetServices()),
then try to connect to each of them directly, one by one
(net.connman.Service.Connect()), and then wait for agent API requests
to come in or for some timeout to expire.
This works, sort of, but only if the first wifi service tried is also
the one which has WPS activated. If the first service tried does *not*
have WPS activated, then I get an error for that service, but at the
same time I can also see in the logs that a connection has actually
been established via WPS with a different access point which *does*
have WPS activated. That latter access point reports a successful WPS
connection and WPS gets disabled there, thinking the client is
alright. Immediately after the connection has been made, it is
disconnected again (probably by ConnMan). Then, when I am trying to
connect to the access point which used to have WPS activated, the
connection attempt fails because WPS has already been deactivated
after the preceding successful connect.
It is actually possible to reproduce this with connmanctl. Connecting
to some "wrong" access point causes WPS to be started with another
access point which has WPS activated, which I think is kind of weird.
I know that I could work around this by asking the user to select an
access point the connection should be made with, but the appliance I
need a solution for does not have any kind of display (save a few
LEDs). For this reason, I really need a fully automated way.
Is this possible? By the way, I am currently using v1.33, and I could
upgrade to any later version if this is required.
Thank you,
Robert
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 27, Issue 4
**************************************
