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. Re: [PATCH] service: Don't auto connect if error is set for
service (Saurav Babu)
2. two wlan interfaces - tether on one and control the other as
a client? (Matthijs Vader)
----------------------------------------------------------------------
Message: 1
Date: Sat, 24 Dec 2016 17:32:57 +0530
From: Saurav Babu <[email protected]>
To: [email protected]
Cc: [email protected], Saurav Babu <[email protected]>
Subject: Re: [PATCH] service: Don't auto connect if error is set for
service
Message-ID:
<[email protected]>
>> In the following scenario:
>> 1. Device gets connected to an AP.
>> 2. Goto AP's settings page and add device's MAC address in block list
>> 3. Device gets disconnected with AP.
>> 4. Auto Connection is again triggered with AP.
>> In above scenario steps 3 and 4 are repeated infintely even though
>> device would never connect to AP because it's MAC address is added in
>> block list of AP.
>> On the first disconnection connect-failed error is set. This patch only
>> blocks auto connection whenever an error is set for the service.
> service_indicate_state() {
> [...]
> switch (new_state) {
> [...]
> case CONNMAN_SERVICE_STATE_DISCONNECT:
> set_error(service,
> CONNMAN_SERVICE_ERROR_UNKNOWN);
> [...]
> }
> [...]
> }
> Is that the source of setting the error variable to
> CONNMAN_SERVICE_ERROR_UNKNOWN?
Yes.
> From a quick look at the pluging tells me that we don't propagate
> or use the disconnect reason code at all. I suspect we would get
> some hint why the disconnect happened. For example if we see reason
> code 4 "Disassociated due to inactivity" would be a non-error reason and
> we would be allowed to reconnect. See table 8-36 in the IEEE 802.11-2012 spec.
> Do you see a reason code in the above scenario?
On most occasions I got reason code as 6 "Class 2 frame received from
nonauthenticated STA" and some occasions reason code 1.
>> ---
>> src/service.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/src/service.c b/src/service.c
>> index 737a39f..e6fdef8 100644
>> --- a/src/service.c
>> +++ b/src/service.c
>> @@ -3733,6 +3733,9 @@ static bool is_ignore(struct connman_service *service)
>> if (service->state == CONNMAN_SERVICE_STATE_FAILURE)
>> return true;
>>
>> + if (service->error != CONNMAN_SERVICE_ERROR_UNKNOWN)
>> + return true;
>> +
>> if (!is_ipconfig_usable(service))
>> return true;
> Looking at the auto_connect_service() code we have following:
> if (is_ignore(service) || service->state !=
>
> CONNMAN_SERVICE_STATE_IDLE)
> continue;
> The service is in CONNMAN_SERVICE_STATE_IDLE state and not in
> CONNMAN_SERVICE_STATE_FAILURE. If so is_ignored() doesn't need to be updated
> (which I would prefer because we are looking only on the service state
> there and not the newtork state)
> So from this, should we set the service state to FAILURE if we have
> a network error code?
Are you trying to say that we should decide to remain to FAILURE state or
change to
IDLE state depending on the reason code?
If yes, then what would be the reason codes on which we should change to IDLE
state
from FAILURE?
Thanks,
Saurav
------------------------------
Message: 2
Date: Sat, 24 Dec 2016 12:08:34 +0000
From: Matthijs Vader <[email protected]>
To: "[email protected]" <[email protected]>
Subject: two wlan interfaces - tether on one and control the other as
a client?
Message-ID:
<he1pr07mb143627642833521f3704ee95c5...@he1pr07mb1436.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
I have two wlan interfaces in linux, from a single rtl8723bu chipset running in
concurrent mode. I want to use wlan0 as a normal client, and use wlan1 to host
an access point. The idea is to use wlan1 to let users of our
blackbox-type-product for setting up eth0 or wlan0 networking and some other
config options.
Is it possible make connman enable tethering on wlan1 only, while also still
using connman to configure & manage the wlan0 as well to connect to other
access points?
All documentation and connmanctl instructions I've seen and use refer to the
more generic wifi..
Or won't that work, and would I be therefore better of keeping connman for the
client (wlan0) only. So make it ignore wlan1 by blacklisting it, and then
setting up hostapd or something similar on wlan1. ?
Best regards, Matthijs
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20161224/bdea8069/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 14, Issue 28
***************************************
