Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] I've always liked the idea of doing up building-wide networks
Date: Fri, 18 Jul 2014 17:31:52 -0700	[thread overview]
Message-ID: <CAA93jw7aBf4=sCM6=Pi0wbKCWgcyGhZpos453m6eJUDpCEfNdg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1407181622190.17284@nftneq.ynat.uz>

I've been looking for a copy of this paper for a long time, and
finally found it.

http://www.eecs.berkeley.edu/~sylvia/cs268-2014/papers//FQ1989.pdf

On Fri, Jul 18, 2014 at 4:25 PM, David Lang <david@lang.hm> wrote:
> On Fri, 18 Jul 2014, Dave Taht wrote:
>
>> ... In particular when it came to getting minimal interference on all
>> the wifi access points. It is better to have fewer, better wifi APs
>> with a co-ordinated channel allocation strategy in an apartment
>> building than everybody installing one willy-nilly.
>
>
> the key is the co-ordinated channel allocation, beyond that it can be better
> to have more, "worse" wifi APs than fewer "better" ones to reduce
> interference.
>
>> http://www.frankston.com/public/?name=20140717-0146
>
>
> looks interesting
>
>
>> BTW: When I find an interesting link, these days, I tend to just put
>> it on my g+ rather than the email lists, and tend to feel I'm wasting
>> other people's bandwidth by doing it on the list - although sometimes
>> a good discussion is sparked. Should I stop forwarding stuff like this
>> (and the mit paper) to the list?
>
>
> to the list, even if it's a link I don't care about, it's easier to delete
> it along with other e-mail than to go to G+ and look at it.
>
> Also, remember that people's G+ feeds show a sampling of what other people
> post, so some people will miss it if you only post it to G+
>
> David Lang



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

      reply	other threads:[~2014-07-19  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 16:13 Dave Taht
2014-07-18 16:46 ` David Personette
2014-07-18 17:35   ` Alijah Ballard
2014-07-18 23:25 ` David Lang
2014-07-19  0:31   ` Dave Taht [this message]

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7aBf4=sCM6=Pi0wbKCWgcyGhZpos453m6eJUDpCEfNdg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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