Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #181479

Re: [A bit OT] Diagnosing home network

Show all headers | View raw

On Fri, May 26, 2017 at 10:09:08AM -0000, Dan Purgert wrote:
> Mark Fletcher wrote:
> > On Sun, May 21, 2017 at 02:18:06PM -0000, Dan Purgert wrote:
> >> Mark Fletcher wrote:
> >> >
> >> 
> > Channel selection is automatic -- shouldn't it pick the clearest one? 
> > Also I am curious as to why selecting 1, 6, 11 or 13 if available is 
> > better and less likely to result in interference?
> 
> "automatic" is a nice way of saying "braindead" in many instances.
> Nearly all gear (until you're spending $1500+ for a single AP) is only
> "auto" when it boots up ... and 9 times out of 10, it'll pull some
> stupid channel like 3.
> 
> The reason for channels 1, 6, or 11 is that 
>  (a) they're universal channels globally
>  (b) they're the only three (2.4 GHz) channels that don't overlap
> 
> For the "standard" channels (1-11), they are 20 MHz wide, and center
> frequencies are spaced 5 MHz apart. This means that channels 1 and 2
> (for example) overlap their spectrum use about 3/4.  In turn, this
> raises the noise floor on both WLANs, leading to garbled packets /
> re-transmissions / other slowdowns -- all of which get mitigated by
> using channels 1,6,11 simply because they don't overlap.
> 
> On the other side - with "everyone" using 1,6,11 - if two APs (or client
> devices) on the same channel are able to "hear" each other, they'll both
> employ their collision avoidance routines to share the channel - even
> when they're on different WLANs.  It's just simple checks along the
> lines of 
> 
>   1. Is anyone transmitting right now?
>     * If yes, wait til they're done, plus random milliseconds, then
>       goto2
>     * If no, wait random milliseconds, then goto2
>   2. Start transmitting 
> 
> 
> It's not perfect, and sometimes you get "hidden node" issues (where say
> your laptop and mine can't hear each other transmit, but our respective
> APs can - they'll then send us the "shutup, someone else is transmitting"
> signal), but instead of both WLANs trying to shout over each other and
> simply generate noise - which near on always slows everything down -
> they share.  Sure, sharing the channel means some degree of slowdown,
> but it's generally not nearly as pronounced as those caused by
> interference.
> 

Fascinating. And makes lots of sense -- thanks! I've entirely left 
channel selection up to the AP so gawd alone knows what channel state I 
am in. I will do battle with the Japanese-language WUI to find out...

Actually maybe I will have more luck interrogating the client side for 
that...

Mark

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-20 07:50 +0200
  Re: [A bit OT] Diagnosing home network Nemeth Gyorgy <friczy@freemail.hu> - 2017-05-20 09:30 +0200
    Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-26 10:10 +0200
  Re: [A bit OT] Diagnosing home network rhkramer@gmail.com - 2017-05-20 12:20 +0200
    Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-26 10:20 +0200
  Re: [A bit OT] Diagnosing home network Gene Heskett <gheskett@shentel.net> - 2017-05-20 15:40 +0200
    Re: [A bit OT] Diagnosing home network Catherine Gramze <rhiamom@mac.com> - 2017-05-20 17:10 +0200
      Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-26 10:20 +0200
    Re: [A bit OT] Diagnosing home network rhkramer@gmail.com - 2017-05-21 19:00 +0200
      Re: [A bit OT] Diagnosing home network Gene Heskett <gheskett@shentel.net> - 2017-05-21 21:20 +0200
      Re: [A bit OT] Diagnosing home network Dan Purgert <dan@djph.net> - 2017-05-22 14:50 +0200
        Re: [A bit OT] Diagnosing home network Gene Heskett <gheskett@shentel.net> - 2017-05-22 17:00 +0200
          Re: [A bit OT] Diagnosing home network Kent West <westk@acu.edu> - 2017-05-22 17:20 +0200
        Re: [A bit OT] Diagnosing home network rhkramer@gmail.com - 2017-05-23 17:30 +0200
          Re: [A bit OT] Diagnosing home network Dan Purgert <dan@djph.net> - 2017-05-24 00:50 +0200
            Re: [A bit OT] Diagnosing home network Brian <ad44@cityscape.co.uk> - 2017-05-24 20:50 +0200
    Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-26 10:20 +0200
      Re: [A bit OT] Diagnosing home network Gene Heskett <gheskett@shentel.net> - 2017-05-26 11:00 +0200
      Re: [A bit OT] Diagnosing home network Curt <curty@free.fr> - 2017-05-27 19:10 +0200
        Re: [A bit OT] Diagnosing home network Dan Purgert <dan@djph.net> - 2017-06-01 13:00 +0200
          Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-06-01 13:30 +0200
            Re: [A bit OT] Diagnosing home network メット <mett@pmars.jp> - 2017-06-01 15:10 +0200
            Re: [A bit OT] Diagnosing home network Dan Purgert <dan@djph.net> - 2017-06-02 12:00 +0200
        Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-06-01 13:10 +0200
  Re: [A bit OT] Diagnosing home network Celejar <celejar@gmail.com> - 2017-05-21 05:50 +0200
  Re: [A bit OT] Diagnosing home network David Christensen <dpchrist@holgerdanske.com> - 2017-05-21 06:10 +0200
  Re: [A bit OT] Diagnosing home network Dan Purgert <dan@djph.net> - 2017-05-21 16:40 +0200
    Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-24 01:40 +0200
    Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-26 10:40 +0200
      Re: [A bit OT] Diagnosing home network Dan Purgert <dan@djph.net> - 2017-05-26 12:30 +0200
        Re: [A bit OT] Diagnosing home network Mark Fletcher <mark27q1@gmail.com> - 2017-05-27 07:20 +0200

csiph-web