Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Aaron Wood <woody77@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Wiring up a wireless testbed
Date: Fri, 3 Nov 2017 16:33:35 -0700	[thread overview]
Message-ID: <CAHb6LvpSKvYrw9qcxS+c0VvkDhX=a5RH8O24q8NKT7AUEqcm7w@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-OSJtXhf2P5Tx3qB22LfaLVhRRUsZO-b=DY6NFOMaXnBw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]

A way I think about is to emulate the "system" in both range/power
(attenuation) and in mixing (phase shifts)   It's a diagonal matrix for
range feeding into an h-matrix for the mixing.  A butler matrix can be used
for the latter if variable phase control isn't required, e.g. you don't
care about spatial stream relative powers.

On adding energy for "random" noise, some knobs of concern are the energy
detect on the tx and signal floor for the rx.   These sources can be fed
into the same h-matrix through their own d-matrices.  This won't replace
field tests but helps get closer towards that while providing for repeat
ability.

Also, equally important by my judgment, though not related to wireless, is
to synchronize the clocks on the PCs.  An oven controlled oscillator and
PTP works well towards that goal.

Bob



On Fri, Nov 3, 2017 at 4:03 PM, Aaron Wood <woody77@gmail.com> wrote:

> What this setup also removes is random noise, which is good for
> repeatability, but bad for real-life testing. My experiences doing similar
> are that there isn’t much of a grey area between a “great”
> throughput/packet error rate and “nothing works”.
>
> It also removes the real-world crosstalk between the antennas.
>
> So good for some things, especially automated tests, but it’s not a
> replacement for real field tests in the presence of random noise.
>
> On Fri, Nov 3, 2017 at 15:51 Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Since I had to (physically) move my wireless testbed recently, I had to
>> figure out a way to run reliable WiFi experiments in a cramped server
>> room. I ended up wiring everything up instead of running over the air,
>> and documented the process here, in case anyone wants to replicate it:
>>
>> https://blog.tohojo.dk/2017/11/building-a-wireless-
>> testbed-with-wires.html
>>
>> Also, if anyone sees any fatal flaw in that setup, please do let me know
>> :)
>>
>> -Toke
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>

[-- Attachment #2: Type: text/html, Size: 3445 bytes --]

  reply	other threads:[~2017-11-03 23:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 22:51 Toke Høiland-Jørgensen
2017-11-03 23:03 ` Aaron Wood
2017-11-03 23:33   ` Bob McMahon [this message]
2017-11-04 21:48     ` Toke Høiland-Jørgensen
2017-11-05  1:50       ` Bob McMahon
2017-11-05  1:56         ` Bob McMahon
2017-11-05  2:04           ` Bob McMahon
2017-11-04 21:46   ` Toke Høiland-Jørgensen
2017-11-04 21:56     ` Aaron Wood
2017-11-04 22:08       ` Toke Høiland-Jørgensen
2017-11-04  7:35 ` Dane Medic
2017-11-04 21:51   ` Toke Høiland-Jørgensen
     [not found] <mailman.928.1509802426.3609.make-wifi-fast@lists.bufferbloat.net>
2017-11-04 14:05 ` Pete Heist

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

  List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHb6LvpSKvYrw9qcxS+c0VvkDhX=a5RH8O24q8NKT7AUEqcm7w@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    --cc=woody77@gmail.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