[145453] in North American Network Operators' Group
Re: meeting network
daemon@ATHENA.MIT.EDU (Richard Barnes)
Mon Oct 10 09:57:47 2011
In-Reply-To: <4E92E93E.5070109@foobar.org>
Date: Mon, 10 Oct 2011 09:56:54 -0400
From: Richard Barnes <richard.barnes@gmail.com>
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
Problem for me at least has not been the MAC layer (either hotel room
or meeting room), it was that the DHCP server was not responding.
Ironically, I could still see everyone's Bonjour and SMB service
advertisements.
--Richard
On Mon, Oct 10, 2011 at 8:46 AM, Nick Hilliard <nick@foobar.org> 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.
>
> if it's wifi that's causing the trouble, the usual causes are:
>
> - 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
>
> There is a more fundamental problem, though: =A0wifi was not designed wit=
h
> crazyass density in mind.
>
> Bring back UTP?
>
> Nick
>
>
