Lets make wifi fast again!
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Pete Heist <pete@eventide.io>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Thu, 26 Apr 2018 15:04:22 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1804261503390.4538@nftneq.ynat.uz> (raw)
In-Reply-To: <38271375-5BAA-41C4-9A84-3967EA41D61C@eventide.io>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 711 bytes --]

On Thu, 26 Apr 2018, Pete Heist wrote:

>> On Apr 26, 2018, at 11:44 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>
>> Hi Pete,
>>
>>> A textual map is below. I use channels 1, 6 and 11 to segment things.
>>
>> Why? I believe in Europe 1, 5, 9, 13 will allow one more independent channel (see https://en.wikipedia.org/wiki/List_of_WLAN_channels). I believe if your site is remote enough that there is nobody else around you might actually be able to get away with 1, 5, 9, 13 ;)
>
> It’s remote enough. I could try it, but some of the equipment I have from the US isn't happy above 11

If you are running OpenWRT, then you should be able to set the country code and 
now worry where the equipment was from.

  reply	other threads:[~2018-04-26 22:04 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
2018-04-26 21:44                   ` Sebastian Moeller
2018-04-26 21:56                     ` Pete Heist
2018-04-26 22:04                       ` David Lang [this message]
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=alpine.DEB.2.02.1804261503390.4538@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=pete@eventide.io \
    /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