IETF Logo Mail Archive

Re: [99attendees] ietf-hotel experience

Randy Bush <randy@psg.com> Tue, 18 July 2017 06:50 UTC

Return-Path: <randy@psg.com>
X-Original-To: 99attendees@ietfa.amsl.com
Delivered-To: 99attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E748131D14 for <99attendees@ietfa.amsl.com>; Mon, 17 Jul 2017 23:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 vYrOgD8uURRu for <99attendees@ietfa.amsl.com>; Mon, 17 Jul 2017 23:50:14 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FFD2131D22 for <99attendees@ietf.org>; Mon, 17 Jul 2017 23:50:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1dXMKi-0001Hd-5r; Tue, 18 Jul 2017 06:50:12 +0000
Date: Tue, 18 Jul 2017 08:50:10 +0200
Message-ID: <m2r2xensrh.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Max Pala <M.Pala@cablelabs.com>
Cc: "99attendees@ietf.org" <99attendees@ietf.org>
In-Reply-To: <3337A025-72B5-4597-ABF7-F6A68ED65405@cablelabs.com>
References: <m2y3rnr1no.wl-randy@psg.com> <18556EFA-2734-460F-B074-E77E49C63508@apache.org> <3337A025-72B5-4597-ABF7-F6A68ED65405@cablelabs.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/99attendees/xwUcAHo22nCKR6fGX4IFe4pFEnA>
Subject: Re: [99attendees] ietf-hotel experience
X-BeenThere: 99attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of IETF 99 attendees that have opted in on this list <99attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/99attendees>, <mailto:99attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/99attendees/>
List-Post: <mailto:99attendees@ietf.org>
List-Help: <mailto:99attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/99attendees>, <mailto:99attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 06:50:15 -0000

> Although yesterday I was able to use the network for basic
> stuff.. today nothing works...
> 
> Most of the times the DHCP fails... then there are DNS resolution
> issues, and, again, lots and lots of packet loss...

and the hack i suggested did not help?

>>> just in case it is helpful to others:
>>> 
>>> this has happened a number of times.  the laptop and i get to our room,
>>> associate with the ietf-hotel ssid wireless, and things work ok for a
>>> minute or three before they go to absolute hell.  i turn my wifi (macos)
>>> off and on again, and things are fine for the rest of the night.
>>> 
>>> the conjecture is my turning wifi off and on again gets me a better
>>> wireless access point.

bummer.  how is the non-hotel-ssid-of-your-choice when not in your room?

and, when you cut a ticket (see network instructions) please describe
your client just in case there are correlations.

the hotel wireless infrastructure is 'interesting.'  the noc is doing
what it can within the connstraints of the hotel infrastructure.

randy

v2.23.0 | Report a Bug | By Email