Re: [72attendees] [Fwd: Re: Update on the Hotel's Guestroom Network]

"Tony Hain" <alh-ietf@tndh.net> Wed, 30 July 2008 16:13 UTC

Return-Path: <72attendees-bounces@ietf.org>
X-Original-To: 72attendees-archive@ietf.org
Delivered-To: ietfarch-72attendees-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AF173A6C0A; Wed, 30 Jul 2008 09:13:25 -0700 (PDT)
X-Original-To: 72attendees@core3.amsl.com
Delivered-To: 72attendees@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 811293A6AC5 for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 16:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.02
X-Spam-Level: *
X-Spam-Status: No, score=1.02 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_STATICB=1.372]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pBEMFXUphKfX for <72attendees@core3.amsl.com>; Tue, 29 Jul 2008 16:53:09 -0700 (PDT)
Received: from tndh.net (static-66-15-163-216.bdsl.verizon.net [66.15.163.216]) by core3.amsl.com (Postfix) with ESMTP id 2787D3A68C8 for <72attendees@ietf.org>; Tue, 29 Jul 2008 16:53:09 -0700 (PDT)
Received: from eagle (192.168.123.10:1832) by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server] id <S17F9B1F> for <72attendees@ietf.org> from <alh-ietf@tndh.net>; Tue, 29 Jul 2008 16:53:19 -0700
From: Tony Hain <alh-ietf@tndh.net>
To: 72attendees@ietf.org
References: <488E1004.6070105@gmail.com>
In-Reply-To:
Date: Wed, 30 Jul 2008 00:53:09 +0100
Message-ID: <02a101c8f1d6$41859cf0$c490d6d0$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acjw3+DN8lA7VFU+SnCUXW2xgoHzkwAdEnGgAB/OkGA=
Content-Language: en-us
X-Mailman-Approved-At: Wed, 30 Jul 2008 09:13:23 -0700
Subject: Re: [72attendees] [Fwd: Re: Update on the Hotel's Guestroom Network]
X-BeenThere: 72attendees@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "Discussion list for the attendees of IETF 72 meeting." <72attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/72attendees>
List-Post: <mailto:72attendees@ietf.org>
List-Help: <mailto:72attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/72attendees>, <mailto:72attendees-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 72attendees-bounces@ietf.org
Errors-To: 72attendees-bounces@ietf.org

Well the hotel network has broken down for me. The Vista host has had open
connections for several hours that are still live, so the system is acting
like a pool has exhausted somewhere. Both the FreeBSD and XP virtual
machines are getting an address, but can't traceroute past 2 hops (necessary
to get to the DNS server). 
traceroute to 159.134.237.6 (159.134.237.6), 64 hops max, 40 byte packets
1  172.17.6.1  4.746 ms  6.370 ms  7.807 ms
2  172.16.110.1  4.867 ms  6.002 ms  6.530 ms
3  * * *
4  * * *

According to the Vista host, the traceroute to the DNS server is:
C:\>tracert -d 159.134.237.6
Tracing route to 159.134.237.6 over a maximum of 30 hops
  1     3 ms     5 ms    15 ms  172.17.6.1
  2     3 ms     4 ms     4 ms  172.16.110.1
  3     3 ms     1 ms     1 ms  10.10.10.254
  4     4 ms     3 ms     3 ms  130.129.64.2
  5     2 ms     2 ms     2 ms  86.43.238.9
  6     2 ms     3 ms     4 ms  159.134.237.6

So we are being double nat'd behind both 172.16.. & 10... space. This would
be consistent with the claims about unexpected connection behavior, and a
sign of the times ahead as the crowd clamors for carrier based nats ... 

Tony

> > -------- Original Message --------
> > Subject: Re: [72attendees] Update on the Hotel's Guestroom Network
> > Date: Mon, 28 Jul 2008 13:55:33 -0400
> > From: Derek Atkins <warlord@pgp.com>
> > To: David Mitton <david@mitton.com>
> > CC: 72attendees@ietf.org, LANGE Andrew <Andrew.Lange@alcatel-
> > lucent.com>
> > References:
> >
> <66F9363AB70F764C96547BD8A0A3679E154B7E@USDALSMBS05.ad3.ad.alcatel.com>
> > <20080728174347.DD7D4257495@smtprelay01.hostedemail.com>
> >
> > What I've just noticed about the HOTEL NAT configuration is that
> every
> > TCP connection gets a different IP address.  There's no consistency,
> > and
> > certainly no long-term bindings.  So every time you hit an HTTP
> server
> > you're hitting it from a different source IP.   This is wreaking
> havoc
> > on my ability to read webmail because every time my source IP changes
> I
> > get logged out!  I suspect that your UDP VPN solution is being hit
> with
> > the same problem.
> >
> > -derek
> >
> > David Mitton wrote:
> > > In my room 38xx, I am currently unable to setup a UDP VPN
> connection
> > to
> > > the US (so called UDP-10000 mode).  The connection is setup but I
> > > receive 0 packets
> > >
> > > But I was successful when I switched to using TCP, port 4005.  I'm
> > using
> > > a Cisco VPN client.
> > >
> > > Dave.
> > >
> > > At 7/28/2008 10:40 AM, LANGE Andrew wrote:
> > >> Content-class: urn:content-classes:message
> > >> Content-Type: multipart/alternative;
> > >>          boundary="----_=_NextPart_001_01C8F0BF.DCD9D701"
> > >>
> > >>
> > >> Because the heavy load on the guest room network is interacting
> > >> negatively with the delivery of video over IP to the TVs in the
> > rooms.
> > >> Certainly CityWest has never experienced traffic loads like we're
> > >> generating from the guest room side, and we're likely uncovering
> > some
> > >> issues in the underlying guest room infrastructure.
> > >>
> > >> The hotel staff has been working this issue since early this
> > morning,
> > >> and they believe that they have fixed the underlying issue causing
> > >> congestion and poor TV performance.  We have lifted the rate-limit
> > on
> > >> the router ports facing the guestroom network.
> > >>
> > >> There has also been a fix put in place on the guestroom network
> that
> > >> was affecting some PPTP users in their rooms.
> > >>
> > >> Both the wireless and terminal room networks, are directly over
> our
> > >> infrastructure and are unaffected by these issues with the
> guestroom
> > side.
> > >>
> > >> Andrew
> > >> _______________________________________________
> > >> 72attendees mailing list
> > >> 72attendees@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/72attendees
> > >
> > > -------------------------------------------------------------------
> --
> > ---
> > >
> > > _______________________________________________
> > > 72attendees mailing list
> > > 72attendees@ietf.org
> > > https://www.ietf.org/mailman/listinfo/72attendees
> >
> >
> > --
> > Derek Atkins
> > Principal Software Engineer
> >
> > PGP Corporation
> > 4 Farragut Ave
> > Somerville, MA  02144
> >
> > +1 617 623 3745 | warlord@pgp.com
> >
> > PGP Corporation -- Rest Secured.(TM)
> >
> > PGP Fingerprint:
> > 0FEE 5EA1 FF22 E0C9 4FFE
> > 631A 9232 FF93 1C80 1DB7

_______________________________________________
72attendees mailing list
72attendees@ietf.org
https://www.ietf.org/mailman/listinfo/72attendees