From: Sebastian Moeller <moeller0@gmx.de>
To: make-wifi-fast@lists.bufferbloat.net,
"Pete Heist" <pete@eventide.io>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Wed, 25 Apr 2018 08:36:09 +0200 [thread overview]
Message-ID: <88966A2D-3C52-4DB1-A079-75260A53C6E4@gmx.de> (raw)
In-Reply-To: <2CD4BD56-8529-4134-8702-B6B89C9ACD91@eventide.io>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hi Pete,
Silly question, are the cabins by chance behind a common breaker? Then maybe you could switch the 'backhaul' to Powerline tech?
On April 25, 2018 8:05:34 AM GMT+02:00, Pete Heist <pete@eventide.io> wrote:
>
>> On Apr 24, 2018, at 11:32 PM, Toke Høiland-Jørgensen <toke@toke.dk>
>wrote:
>>
>> Yeah, with those signal rates, there's going to be quite some pause
>when
>> the slow stations try to transmit something... :/
>
>So then, when would bloat actually become a problem on this hardware? I
>suppose you would need well-connected stations (maybe even just one or
>two) with multiple competing flows. And for the AP to not be one of two
>single channel repeaters with poorly connected stations, where
>contention becomes a problem sooner than bloat.
>
>For starters, I’m going to try to hang one of the two repeaters on the
>same channel off a separate gateway…
>
>_______________________________________________
>Make-wifi-fast mailing list
>Make-wifi-fast@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1588 bytes --]
next prev parent reply other threads:[~2018-04-25 6:36 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 8:33 Pete Heist
2018-04-24 11:54 ` Toke Høiland-Jørgensen
2018-04-24 13:37 ` Pete Heist
2018-04-24 13:51 ` Toke Høiland-Jørgensen
2018-04-24 14:09 ` Pete Heist
2018-04-24 14:34 ` Toke Høiland-Jørgensen
2018-04-24 19:10 ` Pete Heist
2018-04-24 21:32 ` Toke Høiland-Jørgensen
2018-04-25 6:05 ` Pete Heist
2018-04-25 6:36 ` Sebastian Moeller [this message]
2018-04-25 17:17 ` Pete Heist
2018-04-26 0:41 ` David Lang
2018-04-26 19:40 ` Pete Heist
2018-04-26 0:38 ` David Lang
2018-04-26 21:41 ` Pete Heist
2018-04-26 21:44 ` Sebastian Moeller
2018-04-26 21:56 ` Pete Heist
2018-04-26 22:04 ` David Lang
2018-04-26 22:47 ` Pete Heist
2018-04-27 10:15 ` Toke Høiland-Jørgensen
2018-04-27 10:32 ` Pete Heist
2018-04-26 0:35 ` David Lang
2018-04-27 11:42 ` Valent Turkovic
2018-04-27 11:50 ` Pete Heist
2018-04-27 11:59 ` Valent Turkovic
2018-04-27 12:17 ` Pete Heist
2018-04-27 11:47 ` Valent Turkovic
2018-04-27 12:00 ` Pete Heist
2018-05-19 16:03 bkil
2018-05-20 18:56 ` Pete Heist
2018-05-31 0:52 ` David Lang
2018-06-08 9:37 ` Pete Heist
2018-06-09 15:32 ` bkil
2018-06-13 13:07 ` Pete Heist
2018-06-13 13:24 ` Toke Høiland-Jørgensen
2018-06-13 16:01 ` Pete Heist
2018-06-30 19:14 ` bkil
2018-07-04 21:47 ` Pete Heist
2018-07-05 13:08 ` Toke Høiland-Jørgensen
2018-07-05 17:26 ` Pete Heist
2018-07-05 17:37 ` Toke Høiland-Jørgensen
2018-07-05 18:02 ` Pete Heist
2018-07-05 20:17 ` Jonathan Morton
2018-07-09 2:20 ` Aaron Wood
2018-07-09 5:17 ` Jonathan Morton
2018-07-09 6:27 ` Pete Heist
2018-07-09 12:55 ` Sebastian Moeller
2018-07-09 23:21 ` Pete Heist
2018-07-09 5:13 ` David Lang
2018-07-09 23:33 ` Pete Heist
2018-07-10 0:39 ` Pete Heist
2018-07-10 7:02 ` bkil
2018-06-13 16:30 ` Sebastian Moeller
2018-06-13 17:50 ` Toke Høiland-Jørgensen
[not found] ` <CADuVhRWL2aVjzjfLHg1nPFa8Ae-hWrGrE7Wga4eUKon3oqoTXA@mail.gmail.com>
2018-06-30 19:26 ` bkil
2018-06-30 20:04 ` Jannie Hanekom
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=88966A2D-3C52-4DB1-A079-75260A53C6E4@gmx.de \
--to=moeller0@gmx.de \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=pete@eventide.io \
--cc=toke@toke.dk \
/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