From: Pete Heist <pete@eventide.io>
To: David Lang <david@lang.hm>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Thu, 26 Apr 2018 23:41:44 +0200 [thread overview]
Message-ID: <4BB75C5E-243A-4946-98E5-55AE33DA82B7@eventide.io> (raw)
In-Reply-To: <alpine.DEB.2.02.1804251736050.12043@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
> On Apr 26, 2018, at 2:38 AM, David Lang <david@lang.hm> wrote:
>
> can you make a map of how well each AP hears every other AP? (iw scan on each device in turn to report the signal strength of the others)
This should update once per day for a while: http://www.drhleny.cz/smokeping/
A textual map is below. I use channels 1, 6 and 11 to segment things. My biggest problem is on channel 1, where I have two repeaters hanging off of one gateway.
First I’ll try to get cabins 12 and 20 on separate gateways / channels, which will be a challenge with the line-of-sight situation and only three non-overlapping channels. If it isn’t enough, I'll see if I can get anything else cabled or backhauled with 5 GHz. Thanks for the ideas!
CH 1:
ServiceEast sees:
- Cabin12 -69
- Cabin20 -62
Cabin12 sees:
- ServiceEast -66 (gateway)
- Cabin20 -72
Cabin20 sees:
- ServiceEast -62 (gateway)
- Cabin12 -72
CH 6:
ServiceWest sees:
- Cabin28 -50
Cabin28 sees:
- ServiceWest -49 (gateway)
Office sees nothing
CH 11:
Reception sees:
- CabinA1 -68
CabinA1 sees:
- Reception -68 (gateway)
[-- Attachment #2: Type: text/html, Size: 3201 bytes --]
next prev parent reply other threads:[~2018-04-26 21:41 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
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 [this message]
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=4BB75C5E-243A-4946-98E5-55AE33DA82B7@eventide.io \
--to=pete@eventide.io \
--cc=david@lang.hm \
--cc=make-wifi-fast@lists.bufferbloat.net \
--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