[Ietf-62] Re: Contact for network problems at IETF62?

Lars Eggert <lars.eggert@netlab.nec.de> Mon, 07 March 2005 23:15 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15944; Mon, 7 Mar 2005 18:15:07 -0500 (EST)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8RTg-00018L-46; Mon, 07 Mar 2005 18:17:32 -0500
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8RQ7-0002mX-Pe; Mon, 07 Mar 2005 18:13:51 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8PMH-0006CD-NK for ietf-62@megatron.ietf.org; Mon, 07 Mar 2005 16:01:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03449 for <ietf-62@ietf.org>; Mon, 7 Mar 2005 16:01:43 -0500 (EST)
Received: from kyoto.netlab.nec.de ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8POW-0006Zw-Eg for ietf-62@ietf.org; Mon, 07 Mar 2005 16:04:06 -0500
Received: from [] (wireless-130-129-135-204.ietf62.ietf.org []) by kyoto.netlab.nec.de (Postfix) with ESMTP id 869101BAC4D; Mon, 7 Mar 2005 22:01:33 +0100 (CET)
Message-ID: <422CC12B.2030100@netlab.nec.de>
Date: Mon, 07 Mar 2005 15:01:31 -0600
From: Lars Eggert <lars.eggert@netlab.nec.de>
Organization: NEC Network Labs
User-Agent: [Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O) Gecko/20040906 Camino/0.8+]
X-Accept-Language: en,de,es,ja,fr,it,nl,sv,no,da,fi,pt,zh-cn,zh-tw,ko
MIME-Version: 1.0
To: Jim Martin <jim@daedelus.com>
References: <F0DC7B6021F256408935B31D97FC727EA4A725@europa.office>
In-Reply-To: <F0DC7B6021F256408935B31D97FC727EA4A725@europa.office>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
X-Mailman-Approved-At: Mon, 07 Mar 2005 18:13:49 -0500
Cc: ietf-62@ietf.org
Subject: [Ietf-62] Re: Contact for network problems at IETF62?
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>
Content-Type: multipart/mixed; boundary="===============1005301803=="
Sender: ietf-62-bounces@ietf.org
Errors-To: ietf-62-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede


Jim Martin wrote:
> 	Yes, we are aware of issues on the wireless side of the net this 
> morning and are actively working on it. Sorry for the hassle.

is there an update? At least in the sessions I have been in (all in the 
Salons), connectivity was simply absent.

I tried both the unencrypted and the WEP networks and got IP addresses 
in both, but cound not ping the default router and no packets seemed to 
make it passed it either. (I could not associate to the 802.11x network.)

When sessions end, connectivity returns. From my point of view, it seems 
that the problems have shifted from wireless infrastructure to the wired 


PS: I know provisioning IETF wireless networks is a though job. You and 
the other volunteers are doing a terrific job trying to keep us all online!
Lars Eggert                                     NEC Network Laboratories
Ietf-62 mailing list