Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: David Lang <david@lang.hm>
Cc: Aaron Wood <woody77@gmail.com>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] I used to dream of a single wifi cpu, memory, and I/O
Date: Mon, 10 Jul 2023 19:13:34 -0700	[thread overview]
Message-ID: <CAHb6LvrbTh+wvDi1MeKyS+3TUejTcTXV8=wsRc-R-FYcvj_zsw@mail.gmail.com> (raw)
In-Reply-To: <r973385r-s8rq-n4no-q8r4-6o77r901n79q@ynat.uz>


[-- Attachment #1.1: Type: text/plain, Size: 3197 bytes --]

That you can build these networks to operate well says more about you than
the guys supplying parts & equipment. Impressive real world knowledge for
sure.

Bob

On Mon, Jul 10, 2023, 4:34 PM David Lang <david@lang.hm> wrote:

> First off, I am a Huge proponent of getting the RF layout clean before
> anything
> else. Directional signals sound like a fantastic idea, until you realize
> that
> the stations you are talking to are not using directional antennas, then
> the
> value drops significantly (under these conditions, directional antennas
> create
> more hidden transmitters)
>
> When I setup conference wifi, I take advantage of the fact that some walls
> block
> the wifi signals, so I can put the APs closer to the walls that block them
> without worrying about what's on the other side. I also place them on the
> ground
> (under the chairs) as the bodies of the attendees absorb the signal and
> let me
> use more APs in a room than I could get away with otherwise. I also stick
> to the
> standard 10MHz channels, as that lets me re-use a channel with more
> separation
> between APs using the same channel
>
> And yes, I agree that it makes no sense to run an AP at a higher power
> level
> than the stations talking to it, so I turn the power way down.
>
> I haven't knowingly run into the problem you describe of clients
> enumerating all
> available APs, but I may not have setup a high enough density of APs to
> run into
> the problem, can you give more info on that?
>
> > There is no reason to send energy more than 29' as that's the distance
> per
> > fire code that a human has to be from a working smoke detector. and in
> many
> > cities, one can't sell a house without a hard-wired, battery backed up,
> and
> > inter connected smoke detectors.
>
> As someone who has been looking at building a house, it's not that simple.
> Hard
> wired smoke detectors are only needed in some rooms, not in all, and only
> if the
> house is above a minimum size. Then you need different amounts of power to
> get
> through walls depending on how they are built.
>
> When I setup wifi in a conference center exibit hall that's 25,000 sq ft,
> I
> don't believe that there are 80 smoke detectors in that one room (not to
> mention
> the fact that the cealing is more than 29' away, even if I'm standing
> directly
> under it)
>
> Then there's the fact that not everything is inside.
>
> David Lang
>

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.2: Type: text/html, Size: 3730 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  reply	other threads:[~2023-07-11  2:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 21:25 Dave Taht
2023-07-10  5:40 ` Bob McMahon
2023-07-10 19:02   ` Aaron Wood
2023-07-10 20:47     ` Bob McMahon
2023-07-10 21:29       ` David Lang
2023-07-10 22:49         ` Bob McMahon
2023-07-10 23:34           ` David Lang
2023-07-11  2:13             ` Bob McMahon [this message]
2023-07-11  3:02               ` David Lang

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='CAHb6LvrbTh+wvDi1MeKyS+3TUejTcTXV8=wsRc-R-FYcvj_zsw@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=david@lang.hm \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --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