From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com
	[209.85.160.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client CN "smtp.gmail.com",
	Issuer "Google Internet Authority G2" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id AA30421F206
	for <bloat@lists.bufferbloat.net>; Wed, 30 Oct 2013 16:25:38 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id um1so2096694pbc.0
	for <bloat@lists.bufferbloat.net>; Wed, 30 Oct 2013 16:25:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:mime-version
	:content-type:content-transfer-encoding;
	bh=6yBeLmm8lZYSgABx3RgH2aJ/nkYgQ0Kt5FrIfaJh9gI=;
	b=AmBA4okeIlBtxvy5+IqdkicJUy9hz8Eu5AcwSSa/EeaexNE5q7Rw1uTuhaI03TxVrU
	7pVcaGpGW3JxWIZTYtDzs5eQ7db1ggsi291HKDHtc5k0egTBjhREVtBl7SUx+sQR5D94
	8/giS+O1f3Fd3PnCRZL7c20ekHHalTsM7lKvZZuyLu4H356kucyPn8ymVG53hi/un9EU
	RAgmggfphTMRW+o/wu/y1CtReOIg8zlupr+QOjab0cEVBPuCOKrYxbTEIuMRlHWJwJju
	lHR4mdvlypw76wmHlNYyUcHxTkbuoiKNmWVpxuNLGBpMqljJio7gRTmAX4hgBK/QcdSb
	YQAQ==
X-Gm-Message-State: ALoCoQnvYZnRc0tB/oUB3fVGaQFx8T+DRdWKDUudpyTkO6OLSKW9yn3q5UzpCyBT099KAfj2Yifu
X-Received: by 10.66.119.202 with SMTP id kw10mr915770pab.118.1383175537903;
	Wed, 30 Oct 2013 16:25:37 -0700 (PDT)
Received: from nehalam.linuxnetplumber.net
	(static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51])
	by mx.google.com with ESMTPSA id v4sm381164pbq.31.2013.10.30.16.25.37
	for <bloat@lists.bufferbloat.net>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Wed, 30 Oct 2013 16:25:37 -0700 (PDT)
Date: Wed, 30 Oct 2013 16:25:34 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: bloat@lists.bufferbloat.net
Message-ID: <20131030162534.29f34ada@nehalam.linuxnetplumber.net>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [Bloat] T-Mobile LTE buffer bloat
X-BeenThere: bloat@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: General list for discussing Bufferbloat <bloat.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/bloat>
List-Post: <mailto:bloat@lists.bufferbloat.net>
List-Help: <mailto:bloat-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/bloat>,
	<mailto:bloat-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 23:25:38 -0000

I got one of these Samsung LTE hotspot.
Not surprisingly it has huge bloat and a stupid http proxy
that netalyzer claims rewrites images.
 
Bandwidth: Up 1.6 Mbit/sec Down 4.3Mbit/sec
Latency: 140ms 0% loss
Buffering: Uplink 5100ms Down 1800ms

How can the uplink side be so bad! 5 seconds???

Might even return it as defective. You can't even add a review on their
website. Probably they would end taking down like Apple.