From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Debugging connection through Starlink (POINTR)
Date: Mon, 6 Mar 2023 16:47:55 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.2303061645230.11345@nftneq.ynat.uz> (raw)
In-Reply-To: <b70a764b-86e4-8f1d-fd2f-17172d6161ee@auckland.ac.nz>
On Tue, 7 Mar 2023, Ulrich Speidel via Starlink wrote:
> I remember years ago when WiFi in our lecture theatres was new, they'd put
> the access point in the now surplus projectionist's booth at the back. It
> would reach the lectern at the front, so those of us needing WiFi for
> teaching there could set up with connectivity. But then your class would
> enter, and before you knew it, there'd be a couple of dozen laptops and other
> WiFi-enabled devices closer to the access point, and poor me at the front
> would lose connectivity. Of course, any complaints to the powers that be
> would be investigated with lecture theatre empty, and deemed frivolous!
There's also the fact that bodies (full of water) are rather absorbant in the
2.4GHz band, so when there are a lot of people in the room the signal doesn't go
as far.
When I'm setting up wifi for a conference, I take advantage of that to let me
deploy more APs (re-using the channels at closer distances than I could normally
get away with)
David Lang
next prev parent reply other threads:[~2023-03-07 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 11:53 Sauli Kiviranta
2023-02-28 13:14 ` Ulrich Speidel
2023-02-28 14:41 ` Sauli Kiviranta
2023-03-01 20:49 ` Ulrich Speidel
2023-03-06 21:00 ` Sauli Kiviranta
2023-03-06 21:03 ` Nathan Owens
2023-03-06 22:09 ` Ulrich Speidel
2023-03-07 0:47 ` David Lang [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-27 8:58 Sauli Kiviranta
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.2303061645230.11345@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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