Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] treating 2.4ghz as -legacy?
Date: Tue, 17 Dec 2013 21:49:15 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1312172121420.10231@nftneq.ynat.uz> (raw)
In-Reply-To: <20131218050504.GB15289@thunk.org>

On Wed, 18 Dec 2013, Theodore Ts'o wrote:

> On Tue, Dec 17, 2013 at 07:04:54PM -0800, David Lang wrote:
>> As far as I have been able to tell this is purely a software thing.
>> I'm not sure that it's even that it's so complicated as it is that
>> there are no standards for APs to talk to each other to do this sort
>> of thing so nobody has tackled it as an opensource project.
>
> The question is whether you can get the signal strength for a client
> from an AP which isn't associated with the client.  It may not require
> special hardwar, but it would seem to me that it would require special
> firmware in the WiFi device on the AP, right?

I don't believe so. kismit will show all devices without associating with them. 
You can't use it on an active AP, but that's because it wants to scan through 
the different channels. I don't see any reason why you couldn't report the 
signal strength that you do hear.

Now, the fact that you are not scanning will mean that you will probably not see 
the client from all APs, so the smarts in the system will have to know where the 
various APs are, on what channels, and make decisions like 'nobody respond to 
this client on channel 1, AP 53 is on channel 6 and is closer than any AP on 
channel 1.

David Lang

  reply	other threads:[~2013-12-18  5:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 19:46 Dave Taht
2013-12-16 20:19 ` Sebastian Moeller
2013-12-16 20:25 ` Toke Høiland-Jørgensen
2013-12-16 20:48 ` Kelvin Edmison
2013-12-16 21:28 ` David Lang
2013-12-16 22:06   ` Fred Stratton
2013-12-17 17:54     ` Michael Richardson
2013-12-17 18:51       ` Jim Gettys
2013-12-17 22:25         ` dpreed
2013-12-17 22:32           ` Jim Gettys
2013-12-17 23:43             ` Stephen Hemminger
2013-12-18  1:33               ` Theodore Ts'o
2013-12-18  3:04                 ` David Lang
2013-12-18  5:05                   ` Theodore Ts'o
2013-12-18  5:49                     ` David Lang [this message]
2013-12-18 14:17                 ` Chuck Anderson
2013-12-18 15:19               ` dpreed
2013-12-18 16:54                 ` Michael Richardson
2013-12-18 18:18                   ` Toke Høiland-Jørgensen
2013-12-18 19:24                     ` David Lang
2013-12-18 20:07                       ` Michael Richardson
2013-12-18 20:14                         ` David Lang
2013-12-19  9:31                           ` Toke Høiland-Jørgensen
2013-12-19 14:32                             ` Michael Richardson
2013-12-19 20:05                             ` David Lang
2013-12-19 21:01                               ` Chuck Anderson
2013-12-20  0:50                 ` Theodore Ts'o
2013-12-20  5:18                   ` dpreed
2013-12-18 14:06           ` Michael Richardson
2013-12-27 23:56 ` Maciej Soltysiak

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=alpine.DEB.2.02.1312172121420.10231@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=tytso@mit.edu \
    /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