From: "Jean-Pierre Tosoni" <jp.tosoni@acksys.fr>
To: ath10k@lists.infradead.org
Subject: TR: Client station sends probes on DFS channels
Date: Mon, 5 Dec 2016 09:43:55 +0100 [thread overview]
Message-ID: <001c01d24ed3$b6c5ad80$24510880$@acksys.fr> (raw)
In-Reply-To: <CAJ-VmonyohH8qEGMYT5fVAgQ9BskZYj9djYU6mZ1Zp_HEsgdVw@mail.gmail.com>
Just keeping the list informed... At some point the discussion turned private.
Jean-Pierre Tosoni
-----Message d'origine-----
De : Adrian Chadd [mailto:adrian.chadd@gmail.com]
Envoyé : jeudi 1 décembre 2016 19:20
À : Jean-Pierre Tosoni
Objet : Re: Client station sends probes on DFS channels
well, if it fails ETSI certification then you can file a complain with QCA. :) they're passing certification tests with it atm, so...
-a
On 1 December 2016 at 10:18, Jean-Pierre Tosoni <jp.tosoni@acksys.fr> wrote:
> :(
> Can we expect a fix someday?
>
> JP
>
>
>
>> -----Message d'origine-----
>> De : Adrian Chadd [mailto:adrian.chadd@gmail.com] Envoyé : jeudi 1
>> décembre 2016 19:00 À : Jean-Pierre Tosoni Objet : Re: Client station
>> sends probes on DFS channels
>>
>> firmware
>>
>>
>> -a
>>
>>
>> On 1 December 2016 at 09:53, Jean-Pierre Tosoni <jp.tosoni@acksys.fr>
>> wrote:
>> > Hi again,
>> >
>> > That being said, is this 10-minutes delay implemented in ath10k or
>> > in the firmware of the card? Or is it configurable maybe?
>> >
>> > Jean-Pierre
>> >
>> >> -----Message d'origine-----
>> >> De : Adrian Chadd [mailto:adrian.chadd@gmail.com] Envoyé : jeudi 1
>> >> décembre 2016 18:21 À : Jean-Pierre Tosoni Objet : Re: Client
>> >> station sends probes on DFS channels
>> >>
>> >> Hi,
>> >>
>> >> So the implementations I've seen all treat "I see beacons" as "the
>> >> channel is blessed"; there's no logic for doing it for an AP that
>> >> you're associated to.
>> >>
>> >> That's likely what we need clarification around.
>> >>
>> >> The "controlled by a master" doesn't necessarily imply that the
>> >> STA is controlled by the AP, just that the AP has gone through the
>> >> CAC and is doing DFS checking. Otherwise the STA couldn't actually
>> >> send assoc req/response frames, because the station hasn't yet
>> >> associated to an AP to be considered "in control" by it.
>> >>
>> >>
>> >> -adrian
>> >>
>> >>
>> >> On 1 December 2016 at 09:09, Jean-Pierre Tosoni
>> >> <jp.tosoni@acksys.fr>
>> >> wrote:
>> >> > Not quite so.
>> >> >
>> >> >> * if you get a CSA, the STA should move and not use the air
>> >> >
>> >> > No, because the STA is not associated: it is currently searching
>> >> > for an
>> >> AP.
>> >> > So, it cannot receive a CSA, and should do a passive scan.
>> >> >
>> >> >> * if you just start another AP And then kill the APs, there's
>> >> >> nothing above that says when the STA should stop talking?
>> >> >
>> >> > Wrong, the norm says that the STA should *not begin* talking
>> >> > (since it is not associated with a master AP)
>> >> >
>> >> >> -----Message d'origine-----
>> >> >> De : Adrian Chadd [mailto:adrian.chadd@gmail.com] Envoyé :
>> >> >> jeudi 1 décembre 2016 17:53 À : Jean-Pierre Tosoni Cc :
>> >> >> ath10k@lists.infradead.org Objet : Re: Client station sends
>> >> >> probes on DFS channels
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> So to be clear:
>> >> >>
>> >> >> * if you get a CSA, the STA should move and not use the air
>> >> >> * if you just start another AP And then kill the APs, there's
>> >> >> nothing above that says when the STA should stop talking?
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >>
>> >> >>
>> >> >> -adrian
>> >> >
>> >
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2016-12-05 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 18:03 Client station sends probes on DFS channels Jean-Pierre Tosoni
[not found] ` <CAJ-Vmom1EDyHH8Pcuxq83ptsYEGj0LWeDCNvx7gDAUKQmbWZ6g@mail.gmail.com>
2016-12-01 9:13 ` Jean-Pierre Tosoni
2016-12-01 16:53 ` Adrian Chadd
[not found] ` <000001d24bf5$b0c9c690$125d53b0$@acksys.fr>
[not found] ` <CAJ-VmokpLMHL3ND34C4FAW3tVtxHKKOcgSHR9Vs+GsxPwMVE8A@mail.gmail.com>
[not found] ` <000201d24bfb$e0248550$a06d8ff0$@acksys.fr>
[not found] ` <CAJ-Vmo=DabqVwVpBui7gu9p9EBQ_o+o7JGSaKriHvA-OMWBb0A@mail.gmail.com>
[not found] ` <000301d24bff$61d07200$25715600$@acksys.fr>
[not found] ` <CAJ-VmonyohH8qEGMYT5fVAgQ9BskZYj9djYU6mZ1Zp_HEsgdVw@mail.gmail.com>
2016-12-05 8:43 ` Jean-Pierre Tosoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001c01d24ed3$b6c5ad80$24510880$@acksys.fr' \
--to=jp.tosoni@acksys.fr \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox