[90attendees] iPhone wifi weirdness during the conference

Jeff Haas <jhaas@juniper.net> Sat, 26 July 2014 16:06 UTC

Return-Path: <jhaas@juniper.net>
X-Original-To: 90attendees@ietfa.amsl.com
Delivered-To: 90attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FF81B2837 for <90attendees@ietfa.amsl.com>; Sat, 26 Jul 2014 09:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 LEP9DJyWEy5I for <90attendees@ietfa.amsl.com>; Sat, 26 Jul 2014 09:06:01 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0187.outbound.protection.outlook.com [207.46.163.187]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C33B1A0314 for <90attendees@ietf.org>; Sat, 26 Jul 2014 09:06:01 -0700 (PDT)
Received: from [172.29.32.228] (66.129.241.11) by BLUPR05MB152.namprd05.prod.outlook.com (10.255.190.145) with Microsoft SMTP Server (TLS) id 15.0.995.14; Sat, 26 Jul 2014 16:05:58 +0000
From: Jeff Haas <jhaas@juniper.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <6165333F-9180-4002-9870-8EECB528564C@juniper.net>
Date: Sat, 26 Jul 2014 12:05:51 -0400
To: 90attendees@ietf.org
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [66.129.241.11]
X-ClientProxiedBy: BN3PR0301CA0053.namprd03.prod.outlook.com (25.160.152.149) To BLUPR05MB152.namprd05.prod.outlook.com (10.255.190.145)
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:
X-Forefront-PRVS: 02843AA9E0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(6049001)(6009001)(189002)(199002)(30513003)(33656002)(101416001)(81342001)(2351001)(20776003)(107886001)(79102001)(229853001)(81542001)(110136001)(87976001)(106356001)(23726002)(62966002)(47776003)(77156001)(50226001)(4396001)(92566001)(92726001)(77096002)(102836001)(46102001)(107046002)(66066001)(87286001)(21056001)(95666004)(82746002)(83322001)(83072002)(85852003)(46406003)(97756001)(85306003)(83716003)(50466002)(99396002)(105586002)(74502001)(104166001)(50986999)(36756003)(88136002)(42186005)(74662001)(31966008)(80022001)(77982001)(89996001)(76482001)(93916002)(86362001)(104396001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB152; H:[172.29.32.228]; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en;
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/90attendees/odLGEQHDxxs5U4GUBYeA9pzK4lY
Subject: [90attendees] iPhone wifi weirdness during the conference
X-BeenThere: 90attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <90attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/90attendees>, <mailto:90attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/90attendees/>
List-Post: <mailto:90attendees@ietf.org>
List-Help: <mailto:90attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/90attendees>, <mailto:90attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jul 2014 16:06:03 -0000

This is mostly a post-IETF poll to see if others saw similar issues.  Wifi on my laptop (Mac) worked fine throughout the conference.  My iphone on the other hand, seemed to have all sorts of issues with the wifi:
- "ietf" would connect most of the time, but not always give me an address.  Occasionally I'd get ipv6 dns address.
- "ietf-hotel" would connect most regularly, especially in my room but connectivity to the outside world was flakey at best.
- The ietf-a, and all .1x networks simply gave up immediately and fell back to the other config.

Mostly I solved my issues by disabling the wifi and falling back to Rogers.

Did anyone else see similar issues?  

In the future, what sort of troubleshooting is good for diagnosing the root cause of such problems?

-- Jeff