From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>, Joerg Pommnitz <pommnitz@yahoo.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Please don't puke: Modifying Frame Version, Beacon and Probe-Response values
Date: Wed, 1 Jun 2016 12:29:34 -0700 [thread overview]
Message-ID: <574F379E.7050704@candelatech.com> (raw)
In-Reply-To: <CAJ-VmokmAduSkLar6vhL58CPU9BkbQGVeqiqneJRMgSNtuJSMw@mail.gmail.com>
On 06/01/2016 12:18 PM, Adrian Chadd wrote:
> Hi,
>
> Likely a mix of both. Eg, the RX filter stuff as mentioned above may
> mean that you need to listen to /all/ frames for a BSS, rather than
> just say data and beacon frames. If the beacon frame matching logic
> checks the frame version, you need to listen to /all/ of the frames.
>
> For power management things, it's likely none of that will work, so
> you can't use things like auto-sleep based on beacon traffic / timers
> / TIM bitmap - you'd have to keep the NIC awake all the time.
I'm guessing little of this is in hardware, aside from rx filters,
so probably a few tweaks to the firmware would handle much of this...
And, if for AP mode, then the NIC is always awake anyway, right?
Thanks,
Ben
>
>
>
> -adrian
>
>
> On 1 June 2016 at 04:34, Joerg Pommnitz <pommnitz@yahoo.com> wrote:
>> Hi Adrian,
>> does "hardware assist...will likely not work" mean "forget it, won't work"
>> or "so it would have to be implemented in software instead"?
>>
>>
>> -- Regards Joerg
>>
>>
>>
>>> Adrian Chadd <adrian@freebsd.org> schrieb am 17:53 Dienstag, 31.Mai 2016:
>>>> Hi,
>>>
>>> The other thing to keep in mind is the hardware assist for things like
>>> TIM parsing, wakeup, etc will likely not work. :)
>>>
>>>
>>>
>>> -a
>>>
>>>
>>>
>>> On 31 May 2016 at 03:50, Michal Kazior <michal.kazior@tieto.com> wrote:
>>>> On 31 May 2016 at 10:44, jpo <pommnitz@yahoo.com> wrote:
>>>>> Hello all,
>>>>> to implement a "Stealth feature", e.g. the WLAN network does
>>> not show up in
>>>>> normal Scans, we modified the Frame version, Beacon and Probe-Response
>>>>> values for an old ATH5K card running on the now dormant Madwifi driver.
>>>>> Question: Is the same thing even POSSIBLE with ath10k? My main concern
>>> is,
>>>>> that the firmware just won't handle non-standard values.
>>>>>
>>>>> Can somebody who understands the division of labor between mac80211,
>>> ath10k,
>>>>> the firmware and the hardware suppress his or her gag reflex long
>>> enough to
>>>>> think about this?
>>>>
>>>> First and foremost you'll need to use firmware with
>>> "raw-mode" support
>>>> - otherwise firmware just craps over frame headers. Some 10.2.4
>>>> support it - you can look into the mailing list archive for some
>>>> discussions.
>>>>
>>>> Not sure if Rx will work though as firmware-controlled Rx filters may
>>>> prevent you from receiving frames with crazy frame_control values.
>>>> You'll need to check this out yourself. Some firmware revisions might
>>>> have RX_FILTER wmi command support but this isn't used/documented
>>>> anywhere and it's questionable how much it allows you to override.
>>>>
>>>> Whatever you find it'd be nice if you post whatever you find out (for
>>>> posterity :)
>>>>
>>>>
>>>> Michał
>>>>
>>>> _______________________________________________
>>>> ath10k mailing list
>>>> ath10k@lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/ath10k
>>>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-06-01 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 8:44 Please don't puke: Modifying Frame Version, Beacon and Probe-Response values jpo
2016-05-31 10:50 ` Michal Kazior
2016-05-31 15:53 ` Adrian Chadd
2016-06-01 11:34 ` Joerg Pommnitz
2016-06-01 19:18 ` Adrian Chadd
2016-06-01 19:29 ` Ben Greear [this message]
2016-06-01 19:33 ` Adrian Chadd
2016-06-01 19:37 ` Ben Greear
[not found] ` <CAEvAWuHgna4cdgkhQrQY4xo4XyaCAhkkf1zo8iDA_Gqgjc1Jeg@mail.gmail.com>
2016-06-01 19:43 ` Ben Greear
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=574F379E.7050704@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
--cc=pommnitz@yahoo.com \
/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