11:19 p.m.
I wanted to express gratitude for past emails which were very helpful.
I have a test that will connect and disconnect from a given access point.
WIFI=valid access point path
connmanctl connect $WIFI
# wait for connected
connmanctl disconnect $WIFI
#wait for disconnect then repeat
This test works for a few connects/disconnects then I get "Probably roaming right
now!"
However, there's no DBUS signal that anything has changed aka that I'm
"online".
Trying to connect again with connmanctl says I'm all ready connected. But when I check
for a connection via DBUS, it says I'm not connected.
What's going on?
1. What state am I in? Connected/disconnected?
2. How can I know via DBUS what state I'm in?
3. Is there a way to prevent this from happening? Ideally, I'd like to be
"online" as fast as possible like it did the first few connections.
Thanks in advance.
Frederick Ollinger
Software Engineer
Seescan, Inc.
7:49 p.m.
Hi Fred,
On 03/23/2017 12:19 AM, Fred Ollinger wrote:
I wanted to express gratitude for past emails which were very
helpful.
I have a test that will connect and disconnect from a given access point.
WIFI=valid access point path
connmanctl connect $WIFI
# wait for connected
connmanctl disconnect $WIFI
#wait for disconnect then repeat
What kind of hardware are you using? And are you using nl80211 interface
with wpa_supplicant? Is the driver in mainline or is it something closed?
This test works for a few connects/disconnects then I get
"Probably roaming right now!"
wpa_supplicant is coalescing state signals, and ConnMan has to guess
what is happening. The above message says, wpa_supplicant is likely to
switch to a different AP (roaming) but doesn't tell us.
However, there's no DBUS signal that anything has changed aka
that I'm "online".
That is correct if we really roam around.
Trying to connect again with connmanctl says I'm all ready
connected.
But when I check for a connection via DBUS, it says I'm not
connected.
Not sure what happens here. Can you post the exact steps?
What's going on?
Hard to tell. Any logs?
1. What state am I in? Connected/disconnected?
If ConnMan says it is only you should be able to disconnect. If that is
not possible something is broken. Logs?
2. How can I know via DBUS what state I'm in?
Can you run 'monitor-connman' along side and post the log.
Thanks,
Daniel
6:14 p.m.
Thanks, Daniel. This information helped.
My problem is solved.
I was wrong when I said I could not disconnect, I was actually able to do so if I was
connected.
The problem is a result of me not totally understanding the state of "ready" as
opposed to "online". This was explained in a prior email.
What solved my problem is putting timeouts in my test code.
Once I had a timeout (of 30 seconds), I was able to disconnect and continue the test.
Success, in my test was about 97% to connect to a single access point in a test I ran for
48 hours.
So I'd say that connman is doing what it claims that it's doing.
Frederick
________________________________________
From: Daniel Wagner <wagi(a)monom.org>
Sent: Sunday, March 26, 2017 11:49 AM
To: Fred Ollinger; connman(a)lists.01.org
Subject: Re: Probably roaming right now!
Hi Fred,
On 03/23/2017 12:19 AM, Fred Ollinger wrote:
I wanted to express gratitude for past emails which were very
helpful.
I have a test that will connect and disconnect from a given access point.
WIFI=valid access point path
connmanctl connect $WIFI
# wait for connected
connmanctl disconnect $WIFI
#wait for disconnect then repeat
What kind of hardware are you using? And are you using nl80211 interface
with wpa_supplicant? Is the driver in mainline or is it something closed?
This test works for a few connects/disconnects then I get
"Probably roaming right now!"
wpa_supplicant is coalescing state signals, and ConnMan has to guess
what is happening. The above message says, wpa_supplicant is likely to
switch to a different AP (roaming) but doesn't tell us.
However, there's no DBUS signal that anything has changed aka
that I'm "online".
That is correct if we really roam around.
Trying to connect again with connmanctl says I'm all ready
connected.
But when I check for a connection via DBUS, it says I'm not
connected.
Not sure what happens here. Can you post the exact steps?
What's going on?
Hard to tell. Any logs?
1. What state am I in? Connected/disconnected?
If ConnMan says it is only you should be able to disconnect. If that is
not possible something is broken. Logs?
2. How can I know via DBUS what state I'm in?
Can you run 'monitor-connman' along side and post the log.
Thanks,
Daniel
1158
days inactive
1163
days old
2 comments
2 participants
participants (2)
-
Daniel Wagner -
Fred Ollinger