[145454] in North American Network Operators' Group
Re: meeting network
daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Oct 10 09:59:36 2011
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <4E92E93E.5070109@foobar.org>
Date: Mon, 10 Oct 2011 08:57:40 -0400
To: Nick Hilliard <nick@foobar.org>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Oct 10, 2011, at 8:46 AM, Nick Hilliard wrote:
> On 10/10/2011 13:28, Randy Bush wrote:
>> perhaps as an educational exercise in network troubleshooting whoever =
is
>> operating the meeting network could explain what the frack is wrong =
with
>> the meeting network, how it is being debugged, and what they have
>> learned about the cause of the suckage.
>=20
> if it's wifi that's causing the trouble, the usual causes are:
>=20
> - insufficient density of APs for the number of clients
> - APs configured with TX too high (should be set as low as possible)
> - APs configured to accept dot11b <=3D 9 megs
> - APs configured to use auto channel selection
> - stupid broken clients screaming at high volume across the room to =
APs
> which are impossibly far away
>=20
> There is a more fundamental problem, though: wifi was not designed =
with
> crazyass density in mind.
I'm not seeing the problem, but have heard one other person say they are =
having trouble.
Perhaps some details of the problem you are seeing would help diagnose =
the troubles as there are many of us who are not seeing it. I am using =
the 'NANOG-a' network without trouble.
- Jared=
