Re: [93attendees] Hilton Guest Room Internet Update

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 23 July 2015 14:11 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 93attendees@ietfa.amsl.com
Delivered-To: 93attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 390741A1AA3 for <93attendees@ietfa.amsl.com>; Thu, 23 Jul 2015 07:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMNU5avG3L3N for <93attendees@ietfa.amsl.com>; Thu, 23 Jul 2015 07:11:25 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 762BA1A1BCF for <93attendees@ietf.org>; Thu, 23 Jul 2015 07:10:49 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E0FB0205AC for <93attendees@ietf.org>; Thu, 23 Jul 2015 10:12:49 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 50AAC63AEC; Thu, 23 Jul 2015 09:56:00 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3432063AE8 for <93attendees@ietf.org>; Thu, 23 Jul 2015 09:56:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 93attendees@ietf.org
In-Reply-To: <FB562679-F7EC-4BC5-A66D-8F10300248F4@isc.org>
References: <FB562679-F7EC-4BC5-A66D-8F10300248F4@isc.org>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 23 Jul 2015 09:56:00 -0400
Message-ID: <14067.1437659760@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/c12v2aiT0GdmpUvOrp4-m0gIug4>
Subject: Re: [93attendees] Hilton Guest Room Internet Update
X-BeenThere: 93attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 93 attendees that have opted in on this list. " <93attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/93attendees>, <mailto:93attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/93attendees/>
List-Post: <mailto:93attendees@ietf.org>
List-Help: <mailto:93attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/93attendees>, <mailto:93attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2015 14:11:26 -0000

Jim Martin <jrmii@isc.org> wrote:
    > For the wireless, we’ve lit up the “ietf-hotel” ssid on the existing
    > APs, both in the public space and guestrooms. These are the same APs
    > that provide the “hhonors” SSID. While the APs seem to have been
    > originally deployed reasonably, there has been hotel building changes
    > (mostly regarding new sprinkler systems) which has had them moved
    > around in the hallways to very suboptimal locations. This has led to
    > many areas having low to no signal. Additionally, their 2.4G channel
    > assignment and power levels weren’t optimal. Mikenopa has been trying
    > to move APs and reconfigure the channels.

So, a repeat of the Paris IETF effort... :-)

    > Additionally, due to our desire to use public IPv4 space, we’ve seen
    > very high broadcast loads. This is based in the fact that we’ve got a
    > large block that is sparsely used, and thus when we get scanned (as
    > happens constantly from the greater Internet) we get a large amount of
    > ARP traffic which can overload the wireless system. We’ve been working
    > on various techniques to reduce this load.

This seems like a recurring problem, obscured only because of the
one-way-ness of NAT44; that it will get worse as we move to IPv6 everywhere
(with s/ARP/ND/).  I wonder if we need new advice to routers.

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-