Re: [89attendees] When does the IETF network officially come up?

"Dave Oran (oran)" <oran@cisco.com> Sat, 01 March 2014 13:05 UTC

Return-Path: <oran@cisco.com>
X-Original-To: 89attendees@ietfa.amsl.com
Delivered-To: 89attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A054A1A07C4 for <89attendees@ietfa.amsl.com>; Sat, 1 Mar 2014 05:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.047
X-Spam-Level:
X-Spam-Status: No, score=-110.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 52f-nc3BAHHZ for <89attendees@ietfa.amsl.com>; Sat, 1 Mar 2014 05:05:18 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id A3FEA1A07BC for <89attendees@ietf.org>; Sat, 1 Mar 2014 05:05:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10366; q=dns/txt; s=iport; t=1393679116; x=1394888716; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MRnUC4vJFEcZg+spYVk9fbjdRvavM/9EcMGBcMn2KFM=; b=ll9T5U4rKPK+ws1ELAXRv+qytDxi0DEXe1AnXqSfC0J9JIRVI/peNxtQ LjS6YFHgdbct2EhGtX4Fdvkxj21r6ZuJ2YqzZEaXc0FhIf6aRhhel6Ezz oAGv2HpASjmMJWpGEw4hG9XCqi6+l0VTUcvTCUzQNgtks3knRZKSUvLdB w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FANvZEVOtJV2Y/2dsb2JhbABVA4MGO8ElT4ETFnSCJgEBBAEBAUYlCxACAQgHByABEAcnCxQRAQEEDgWHeQ3LWReNcxEBCQI1DAQHCQgBAYMRgRQEmDySK4MtgWoHFw
X-IronPort-AV: E=Sophos; i="4.97,568,1389744000"; d="scan'208,217"; a="24173008"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP; 01 Mar 2014 13:05:16 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s21D5Gmk018949 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 1 Mar 2014 13:05:16 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.150]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Sat, 1 Mar 2014 07:05:15 -0600
From: "Dave Oran (oran)" <oran@cisco.com>
To: Jim Martin <jrmii@isc.org>
Thread-Topic: [89attendees] When does the IETF network officially come up?
Thread-Index: Ac81PqhBFgFPbBl7T+SLgUBoKoqZcgANzEKAAACrzwAAAGvjAP//qVUe
Date: Sat, 1 Mar 2014 13:05:14 +0000
Message-ID: <9B214294-5B21-43A5-9E1F-08B6630323F1@cisco.com>
References: <884C5283-E928-478B-922A-9B9347A41EDB@cisco.com> <CACbUdyqLQFT8y+w0mMynceLrYFyXpT7oPZYZnApJGOcYHk+Q9g@mail.gmail.com> <6C1E7012-198E-41B5-BC0A-0D89307CB6A8@isoc.org>, <9AD8EDB5-DA02-4956-9AB4-FF965CFA714E@isc.org>
In-Reply-To: <9AD8EDB5-DA02-4956-9AB4-FF965CFA714E@isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_9B2142945B2143A59E1F08B6630323F1ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/89attendees/02kJHlod1bBDsNghbQtpCTNWumA
Cc: Ray Pelletier <rpelletier@isoc.org>, Colin Doyle <cdoyle@verilan.com>, attendees <89attendees@ietf.org>
Subject: Re: [89attendees] When does the IETF network officially come up?
X-BeenThere: 89attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 89 attendees that have opted in to the list." <89attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/89attendees>, <mailto:89attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/89attendees/>
List-Post: <mailto:89attendees@ietf.org>
List-Help: <mailto:89attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/89attendees>, <mailto:89attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Mar 2014 13:05:21 -0000

Thanks,

I called it in and got vectored to a Tech support person at BT, who had to ask which city I was in :-).
Managed to get her to abort the normal support script and explained I knew what I was doing.
She obviously couldn't help with the wired Ethernet, and said the only thing she could try was to reboot the AP, which she promised to do. If the problem is coverage, that's not going to help...

I'm highly suspicious it's just bad RF coverage, since I just decided to sit on the bed at the other side of the room and it's staying up now.

Unfortunately I can't do real work in this mode, so, if Ings don't improve I'll ask to change rooms.

DaveO

On Mar 1, 2014, at 12:15 PM, "Jim Martin" <jrmii@isc.org<mailto:jrmii@isc.org>> wrote:

Ray,
As we've discussed, that's an artifact of the Hilton gateway/accounting system. If you use the ietf-hotel or the wired connection, you connect (using the hotel's infrastructure) to the IETF network, with native IPv4 and IPv6 and no rate-limits or device limitations.

That all said, to echo Chris and Colin's comments, if you're having wifi signal strength issues or link issues on your wired connection, please call the normal hotel support number, as we don't have access to their switches or APs. However, if you're having any IPv4 or IPv6 related issues (anything above the wire) please let the NOC know at tickets@meeting.ietf.org<mailto:tickets@meeting.ietf.org>, or catch us in the Terminal Room in Hilton Meeting Rooms 13-17.

- Jim

On Mar 1, 2014, at 12:03 PM, Ray Pelletier <rpelletier@isoc.org<mailto:rpelletier@isoc.org>> wrote:

I was also advised that there was a 3 device limitation to each room.

Ray
On Mar 1, 2014, at 6:44 AM, Colin Doyle <cdoyle@verilan.com<mailto:cdoyle@verilan.com>> wrote:


It's more then likely the WAP you are associated to. As is standard SOP, the hotel SSID's and the itef guest room SSID are being beaconed from the same devices. It's only in the meeting rooms and some public areas where we deploy our own gear.

Since your wire is dead and your Wi-Fi is wonky, you'll want to call the front desk to get in touch with the guest room network help desk. They are the ones who can assist with physical layer issues in the rooms.

C

--

Colin Doyle, CCNA, F5 ASP/ATSP, Juniper JES
Director of Network Services
Verilan, Inc.
7327 SW Barnes Rd. #215
Portland, OR 97225

+1 503.810.2129 [mobile]
cdoyle@verilan.com<mailto:cdoyle@verilan.com> [email]
cdoyle.verilan [skype]
www.verilan.com<http://www.verilan.com/> [website]

This e-mail contains proprietary information and may be confidential. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you received this message in error, please delete it immediately.

On Mar 1, 2014 11:09 AM, "Dave Oran (oran)" <oran@cisco.com<mailto:oran@cisco.com>> wrote:
It's Saturday AM and I'm in my room on the tenth floor of the Hilton Metropole.

- the wired Ethernet in the room is totally dead (no signal)
- wifi connections to IETF-hotel stay are not usable - either joining the network fails, or the connection drops within 20-30 seconds.
- honors said is non-functional too - I can't get redirected to the portal login with any reliability.

Is this just me? Symptoms are identical for WiFi on here devices (Mac, iPad, iPhone)

_______________________________________________
89attendees mailing list
89attendees@ietf.org<mailto:89attendees@ietf.org>
https://www.ietf.org/mailman/listinfo/89attendees
_______________________________________________
89attendees mailing list
89attendees@ietf.org<mailto:89attendees@ietf.org>
https://www.ietf.org/mailman/listinfo/89attendees

_______________________________________________
89attendees mailing list
89attendees@ietf.org<mailto:89attendees@ietf.org>
https://www.ietf.org/mailman/listinfo/89attendees