From: Johannes Berg <johannes@sipsolutions.net>
To: Allan Matthew <allanm84@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: set channel from radiotap headers during injection
Date: Wed, 19 Aug 2015 21:41:02 +0200 [thread overview]
Message-ID: <1440013262.2089.13.camel@sipsolutions.net> (raw)
In-Reply-To: <CAEnVuW0m5jPMcQnC4inVF+8xubZbuyM-faP6Lebz26jvb4s-XA@mail.gmail.com> (sfid-20150819_210044_577870_EE440EEF)
On Wed, 2015-08-19 at 12:00 -0700, Allan Matthew wrote:
>
> I operate an AP on one channel that talks to some set of devices.
>
> On another "channel" (maybe just different BW) I use packet injection
> to send data to and from a separate device.
>
> The bitrate to the 2nd device (on the 2nd channel) is much lower than
> that of the AP, and I'd like to get longer range out of it. The idea
> is that I use narrower bandwidth and fixed, low bitrates with control
> over the retries to get really tight control over that link.
>
It might be somewhat feasible to set up the second one as a regular
client/AP link as well, with a different channel context...
However, the clients on the original AP might not be amused - their AP
would mysteriously disappear every once a while, something they're not
expecting (unless you restrict it to P2P GO/client operation)
johannes
next prev parent reply other threads:[~2015-08-19 19:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 18:22 set channel from radiotap headers during injection Allan Matthew
2015-08-14 21:39 ` Allan Matthew
2015-08-19 11:24 ` Johannes Berg
2015-08-19 16:37 ` Allan Matthew
2015-08-19 18:09 ` Johannes Berg
2015-08-19 19:00 ` Allan Matthew
2015-08-19 19:41 ` Johannes Berg [this message]
2015-08-19 19:50 ` Allan Matthew
2015-08-19 19:53 ` Johannes Berg
2015-08-19 20:43 ` Allan Matthew
2015-08-25 0:46 ` Allan Matthew
2015-08-25 9:36 ` Johannes Berg
2015-08-25 17:47 ` Allan Matthew
2015-08-25 17:48 ` Johannes Berg
2015-08-19 17:44 ` Ben Greear
2015-08-19 18:02 ` Johannes Berg
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=1440013262.2089.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=allanm84@gmail.com \
--cc=linux-wireless@vger.kernel.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 NNTP newsgroup(s).