[Ietf-62] Re: IETF62 Wireless Network Update

Emmanuel.Desmet@alcatel.com Tue, 08 March 2005 13:07 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20868; Tue, 8 Mar 2005 08:07:34 -0500 (EST)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8eTM-0003xG-4p; Tue, 08 Mar 2005 08:10:04 -0500
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8eQ5-00086B-TO; Tue, 08 Mar 2005 08:06:41 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8StI-0007vF-Ka for ietf-62@megatron.ietf.org; Mon, 07 Mar 2005 19:48:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00747 for <ietf-62@ietf.org>; Mon, 7 Mar 2005 19:48:01 -0500 (EST)
From: Emmanuel.Desmet@alcatel.com
Received: from smail.alcatel.fr ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8SvY-00052J-B2 for ietf-62@ietf.org; Mon, 07 Mar 2005 19:50:26 -0500
Received: from bemail01.netfr.alcatel.fr (bemail01.netfr.alcatel.fr []) by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id j280ll9B030419; Tue, 8 Mar 2005 01:47:56 +0100
In-Reply-To: <8bdae40f57cc3a718719567bc48158f0@daedelus.com>
To: Jim Martin <jim@daedelus.com>
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFA65C6335.9D352034-ONC1256FBE.000415FD-C1256FBE.00045FC3@netfr.alcatel.fr>
Date: Tue, 8 Mar 2005 01:47:46 +0100
X-MIMETrack: Serialize by Router on BEMAIL01/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 03/08/2005 01:47:55
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-Mailman-Approved-At: Tue, 08 Mar 2005 08:06:40 -0500
Cc: ietf-62@ietf.org
Subject: [Ietf-62] Re: IETF62 Wireless Network Update
X-BeenThere: ietf-62@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-62 Mailing List <ietf-62.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-62>, <mailto:ietf-62-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ietf-62>
List-Post: <mailto:ietf-62@lists.ietf.org>
List-Help: <mailto:ietf-62-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-62>, <mailto:ietf-62-request@lists.ietf.org?subject=subscribe>
Sender: ietf-62-bounces@ietf.org
Errors-To: ietf-62-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976

Note that I'm not at all an expert in these matters (far from it actually)
but looks to me that there are apparently also dns problems on floor 3 that
are not occuring at all on e.g. the ground floor.

At least that's my personal non-expert diagnosis as opposed to the DHCP
ones mentioned below.

Gentle as always,

@+ manu

                      Jim Martin                                                                                                     
                      <jim@daedelus.co         To:      ietf@ietf.org                                                                
                      m>                       cc:                                                                                   
                      Sent by:                 Subject: IETF62 Wireless Network Update                                               
                      08/03/2005 01:33                                                                                               

             We just wanted to give everyone an update on the state of the
network here at the Hilton. As most people noticed, we had severe
problems involving APs going away starting right around 9am when the
first meetings began. We identified and worked around the problem and
the APs have been up and reasonably solid since mid-morning.

             However, despite the APs staying up, we continued to see
particularly on the 3rd floor.  Common symptoms were:
             - Long delays before receiving DHCP responses
             - Long first hop round trip times
             - Loss on the first hop (in the wireless domain)
             - Receiving a DHCP address, but still not having the ability
contact the default router

             Moving forward, we've made several configuration changes which
help matters, and we believe that most of the problems have been
resolved. Please (gently) let us know if you're still seeing major
problems. The 2.4G band (802.11b/g) is still pretty congested and has
some inherent issues in a situation like IETF meetings, so if you have
the option to use 802.11a, we'd suggest you do so.

             As always, any trouble reports or questions can be directed at


             Again, our apologies for the frustration and annoyance this is

causing. Believe us, we want to get this to work just as much, if not
more, than you all do!

             - Jim

Ietf mailing list

Ietf-62 mailing list