From: jpo <jpo2341-ath9k@yahoo.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Unusal question: ATH9k and broken-on-purpose 802.11 frames
Date: Thu, 25 Aug 2016 12:10:20 +0000 (UTC) [thread overview]
Message-ID: <1014456101.10974427.1472127020394.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: 1014456101.10974427.1472127020394.JavaMail.yahoo.ref@mail.yahoo.com
Hello all,
due to difficult to explain reasons that involve customers that believe in security by obscurity I made some modifications to the then current Madwifi driver for older Atheros chips. Specifically, I changed some values in the frame control field (version number, beacon and probe response values). This way IBSS networks with our modifications would not show up in a normal scan.
Fast forward to 2016: It's becoming harder to source the old hardware (both the WLAN card and actual CPU boards that support miniPCI instead of PCIe). That's why we have to upgrade our hardware. Selecting a WLAN card seems to be the most troublesome part, because most cards only support consumer grade instead of the extended industrial specs (-40..85 ?C) we need. We have narrowed the field down to ath9k or ath10k based cards (BTW: I'm open to alternative suggestions here!). ATH10K is problematic, because it would need a modified firmware blob and doesn't support IBSS out of the box.
That's why our strong preference is to go with ath9k. Since the very first Atheros 802.11n cards were supported by the old Madwifi driver, I would assume that there are no major obstacles to support the broken-on-purpose 802.11 frames. Am I right? Is there anything that I should keep in mind? Does the hardware filter invalid frames? If so, can I disable or change these filters?
Thanks in advance and kind regards
Joerg
parent reply other threads:[~2016-08-25 12:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1014456101.10974427.1472127020394.JavaMail.yahoo.ref@mail.yahoo.com>]
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=1014456101.10974427.1472127020394.JavaMail.yahoo@mail.yahoo.com \
--to=jpo2341-ath9k@yahoo.com \
--cc=ath9k-devel@lists.ath9k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).