meeting network

Randy Carpenter rcarpen at
Mon Oct 10 14:20:22 UTC 2011

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 extremely slow, or non responsive. The hotel appears to be shoving all traffic through a squid proxy, which does not appear to be big enough to handle the traffic. I have gotten various error messages from squid.

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


On Oct 10, 2011, at 10:01, Owen DeLong <owen at> wrote:

> On Oct 10, 2011, at 6:50 AM, Christopher Morrow wrote:
>> On Mon, Oct 10, 2011 at 9:01 AM, Dobbins, Roland <rdobbins at> wrote:
>>> On Oct 10, 2011, at 7:46 PM, Nick Hilliard wrote:
>>>> if it's wifi that's causing the trouble, the usual causes are:
>> 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!)
>> 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?)
>> -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

More information about the NANOG mailing list