[145457] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: meeting network

daemon@ATHENA.MIT.EDU (Randy Carpenter)
Mon Oct 10 10:22:30 2011

From: Randy Carpenter <rcarpen@network1.net>
In-Reply-To: <DEDD92E0-16BC-4F1F-B7F4-B9FF99DED377@delong.com>
Date: Mon, 10 Oct 2011 10:20:22 -0400 (EDT)
To: Owen DeLong <owen@delong.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On the hotel network, I have also seen some issues beyond getting an address=
. I can usually trace just fine, but applications, specifically web is extre=
mely slow, or non responsive. The hotel appears to be shoving all traffic th=
rough a squid proxy, which does not appear to be big enough to handle the tr=
affic. I have gotten various error messages from squid.

I would think that the contract with the hotel for the conference would incl=
ude the specific requirements for the network. Is that not the case?

-Randy

On Oct 10, 2011, at 10:01, Owen DeLong <owen@delong.com> wrote:

>=20
> On Oct 10, 2011, at 6:50 AM, Christopher Morrow wrote:
>=20
>> On Mon, Oct 10, 2011 at 9:01 AM, Dobbins, Roland <rdobbins@arbor.net> wro=
te:
>>> 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
>=20
> It would be wise for NANOG to approach future venues and specifically disc=
uss these things with the hotel IT departments in question ahead of time so t=
hat they have some remote chance of being prepared.
>=20
> Owen
>=20
>=20
>=20


home help back first fref pref prev next nref lref last post