Send connman mailing list submissions to
        connman@lists.01.org

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
        connman-requ...@lists.01.org

You can reach the person managing the list at
        connman-ow...@lists.01.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."


Today's Topics:

   1. [PATCH v2] dbus.h: Update include/dbus.h to remove unused
      macro (Harish Jenny K N)
   2. Re: When BackgroundScanning = false, connman's Scan() dbus
      method is broken (Jose Blanquicet)
   3. Re: When BackgroundScanning = false, connman's Scan() dbus
      method is broken (Jonah Petri)


----------------------------------------------------------------------

Message: 1
Date: Fri, 11 Aug 2017 11:32:12 +0530
From: Harish Jenny K N <harish_kand...@mentor.com>
To: <conn...@connman.net>
Subject: [PATCH v2] dbus.h: Update include/dbus.h to remove unused
        macro
Message-ID:
        <1502431332-9370-1-git-send-email-harish_kand...@mentor.com>
Content-Type: text/plain

CONNMAN_DEBUG_INTERFACE and CONNMAN_PROVIDER_INTERFACE
is not used anymore. Hence remove this from include/dbus.h

---
 include/dbus.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/include/dbus.h b/include/dbus.h
index 26f94d6..bcab418 100644
--- a/include/dbus.h
+++ b/include/dbus.h
@@ -31,7 +31,6 @@ extern "C" {
 #define CONNMAN_SERVICE                        "net.connman"
 #define CONNMAN_PATH                   "/net/connman"

-#define CONNMAN_DEBUG_INTERFACE                CONNMAN_SERVICE ".Debug"
 #define CONNMAN_ERROR_INTERFACE                CONNMAN_SERVICE ".Error"
 #define CONNMAN_AGENT_INTERFACE                CONNMAN_SERVICE ".Agent"
 #define CONNMAN_COUNTER_INTERFACE      CONNMAN_SERVICE ".Counter"
@@ -42,7 +41,6 @@ extern "C" {
 #define CONNMAN_CLOCK_INTERFACE                CONNMAN_SERVICE ".Clock"
 #define CONNMAN_TASK_INTERFACE         CONNMAN_SERVICE ".Task"
 #define CONNMAN_SERVICE_INTERFACE      CONNMAN_SERVICE ".Service"
-#define CONNMAN_PROVIDER_INTERFACE     CONNMAN_SERVICE ".Provider"
 #define CONNMAN_TECHNOLOGY_INTERFACE   CONNMAN_SERVICE ".Technology"
 #define CONNMAN_SESSION_INTERFACE      CONNMAN_SERVICE ".Session"
 #define CONNMAN_NOTIFICATION_INTERFACE CONNMAN_SERVICE ".Notification"
--
1.9.1




------------------------------

Message: 2
Date: Fri, 11 Aug 2017 08:43:24 +0200
From: Jose Blanquicet <blanqui...@gmail.com>
To: Jonah Petri <jo...@sense.com>
Cc: Daniel Wagner <w...@monom.org>, connman@lists.01.org,  Sam Nazarko
        <em...@samnazarko.co.uk>
Subject: Re: When BackgroundScanning = false, connman's Scan() dbus
        method is broken
Message-ID:
        <cafc8ijj6b31briwvfq-v4vvztip7dfrfzg8sg4mwq6b20ix...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Good morning Jonah,

I think I got something.

On Thu, Aug 10, 2017 at 4:51 PM, Jonah Petri <jo...@sense.com> wrote:
> What I see empirically is that with the brcmfmac driver on a bcm 43430
chip, on linux 4.1.15, the max_ssids is reported as 10. I am definitely a
novice when it comes to anything below wpa_supplicant, but could it be that
active scan only probes for the specifically-mentioned networks? From my
reading, this active scanning mechanism seems to be intended for finding
specific SSIDs, e.g. hidden SSIDs. However, empirically in my case, if the
MAC can't see the requested network, it does not report any scan results at
all.

I missed something here. In active scan request we are asking
wpa_supplicant to look for specific SSIDs in specific channels. In my case,
I had a lot of "known-services" then basically the active request includes
a lot of channels and that's what I continue seeing many APs in range. To
confirm this theory, I let only one folder in {STOREDIR}/connman/wifi_* and
I modified the settings file of that remaining services by changing the
frequency to a 5GHz channel. Then I forced ConnMan to handle only an
interface which I know only supports 2.4GHz. Doing so ConnMan would ask an
active scan only in that 5GHz channel and then the scan result should be
empty. The results confirmed this idea and I could reproduce this issue,
scan list was empty.

So, according to the your dbus logs, there should not exist any AP using
2437 in your range, is it true? Try to do what I did and modify the
settings file of your "known-service" to a frequency you are sure there are
APs in your range. Doing so you should be able see them now. Remember to
kill ConnMan before modifying that settings file then re-launch ConnMan or
just reboot your system to get the changes applied.

> My 2?: If "Active" scanning will indeed only return results for the SSIDs
mentioned in the scan parameters, then I think ConnMan should *always*
schedule a passive scan afterwards, perhaps by just calling
wifi_scan_simple() in the scan_callback() of an active scan.
>
> Thoughts?

That sounds reasonable. You should just take into account the timing, you
cannot immediately ask wpa_supplicant for another scan because it could
just be discarded due to there is another ongoing. That second passive scan
needs to be done once you are sure the active scan has finished. You could
try to implement this, I will think if this is the best we can do. Then we
can test and discuss the options.

As always comments/suggestions are welcomed.

Regards,

Jose Blanquicet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20170811/f05bd6cb/attachment-0001.html>

------------------------------

Message: 3
Date: Fri, 11 Aug 2017 10:24:39 -0400
From: Jonah Petri <jo...@sense.com>
To: Jose Blanquicet <blanqui...@gmail.com>
Cc: Daniel Wagner <w...@monom.org>, connman@lists.01.org, Sam Nazarko
        <em...@samnazarko.co.uk>
Subject: Re: When BackgroundScanning = false, connman's Scan() dbus
        method is broken
Message-ID: <a6b46532-ae15-4c81-8550-b19c8eca1...@sense.com>
Content-Type: text/plain; charset="utf-8"

Good morning, Jose!

Thanks for checking into this.

> On Aug 11, 2017, at 2:43 AM, Jose Blanquicet <blanqui...@gmail.com> wrote:
> 
> ]So, according to the your dbus logs, there should not exist any AP using 
> 2437 in your range, is it true? Try to do what I did and modify the settings 
> file of your "known-service" to a frequency you are sure there are APs in 
> your range. Doing so you should be able see them now. Remember to kill 
> ConnMan before modifying that settings file then re-launch ConnMan or just 
> reboot your system to get the changes applied.
> 

There are 6 other networks using 2437 in range.  I am in a downtown area with 
LOTS of APs.  So that's not it.

> > My 2?: If "Active" scanning will indeed only return results for the SSIDs 
> > mentioned in the scan parameters, then I think ConnMan should *always* 
> > schedule a passive scan afterwards, perhaps by just calling 
> > wifi_scan_simple() in the scan_callback() of an active scan.
> >
> > Thoughts?
> 
> That sounds reasonable. You should just take into account the timing, you 
> cannot immediately ask wpa_supplicant for another scan because it could just 
> be discarded due to there is another ongoing. That second passive scan needs 
> to be done once you are sure the active scan has finished. You could try to 
> implement this, I will think if this is the best we can do. Then we can test 
> and discuss the options.

Can you say more about the expected behavior of wpa_supplicant?  The wpa_s dbus 
docs say nothing about scans being ignored, so now I'm worried that I can't 
trust them.  https://w1.fi/wpa_supplicant/devel/dbus.html 
<https://w1.fi/wpa_supplicant/devel/dbus.html>

Best,

Jonah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20170811/3cd604c3/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
connman@lists.01.org
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 22, Issue 11
***************************************

Reply via email to