[145456] in North American Network Operators' Group
Re: meeting network
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Oct 10 10:02:24 2011
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAL9jLaZ=1TCDk9k_u2GxCdeSZwfJGRk_R7nkoZQOTr=jxVBORA@mail.gmail.com>
Date: Mon, 10 Oct 2011 07:00:43 -0700
To: Christopher Morrow <morrowc.lists@gmail.com>
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 6:50 AM, Christopher Morrow wrote:
> On Mon, Oct 10, 2011 at 9:01 AM, Dobbins, Roland <rdobbins@arbor.net> =
wrote:
>> On Oct 10, 2011, at 7:46 PM, Nick Hilliard wrote:
>>=20
>>> if it's wifi that's causing the trouble, the usual causes are:
>=20
> is the complaint the hotel ROOM wireless? or the meeting-room? I
> noticed the nanog-a-secure bounce me 2x, so I moved back to
> ipsec-tunnel on nanog-a.. in the past nanog (plain) has been more
> 'stable' for me in general (and all you mac users can happily fight
> over -a!)
>=20
> As to the hotel room wifi... apparently when you have 490 rooms in the
> hotel (full) and only provision your internal NAT space as a /23 ...
> things work 'fine' most days. When a networking conference comes to
> visit with 3+ devices requiring IP in each room... the whole hotel
> network stops :( Last night the display systems in the lobby and the
> hotel registration machines were all broken :( The hotel's network
> people (in NYC) are supposedly 'on a fix', who knows... (is expanding
> the nat subnet THAT hard?)
>=20
> -chris
It would be wise for NANOG to approach future venues and specifically =
discuss these things with the hotel IT departments in question ahead of =
time so that they have some remote chance of being prepared.
Owen
