Delivery-Date: Mon, 02 Feb 2015 00:10:16 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 432CD1E0B9F
	for <archiver@seul.org>; Mon,  2 Feb 2015 00:10:14 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A4D5C33399;
	Mon,  2 Feb 2015 05:10:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5D67333394
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 05:10:06 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id qMQNXmM-lJ6w for <tor-talk@lists.torproject.org>;
 Mon,  2 Feb 2015 05:10:06 +0000 (UTC)
Received: from relay.ox.registrar-servers.com (relay.ox.registrar-servers.com
 [199.188.203.174])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.registrar-servers.com",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 276B833342
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 05:10:06 +0000 (UTC)
X-Greylist: delayed 401 seconds by postgrey-1.34 at eugeni;
 Mon, 02 Feb 2015 05:10:06 UTC
Received: (qmail 25400 invoked by uid 89); 2 Feb 2015 05:03:21 -0000
Received: from unknown (HELO imap10-3.ox.privateemail.com) (192.64.116.216)
 by relay.ox.registrar-servers.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
 2 Feb 2015 05:03:21 -0000
Received: from localhost (localhost [127.0.0.1])
 by mail.privateemail.com (Postfix) with ESMTP id 3E5182400AA
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:02:47 -0500 (EST)
X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com
Received: from mail.privateemail.com ([127.0.0.1])
 by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id xkI_0rN5dHoW for <tor-talk@lists.torproject.org>;
 Mon,  2 Feb 2015 00:02:47 -0500 (EST)
Received: from 127.0.0.1 (politkovskaja.torservers.net [77.247.181.165])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.privateemail.com (Postfix) with ESMTPSA id 721EA2400A9
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:02:45 -0500 (EST)
Message-ID: <54CF04F2.1060806@austinhartzheim.me>
Date: Mon, 02 Feb 2015 05:02:42 +0000
From: Austin Hartzheim <austin@austinhartzheim.me>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
In-Reply-To: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
Subject: Re: [tor-talk] ISP CenturyLink Blocking Tor?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

nathaniel@moltennetworks.co.uk:
> I have been at a close friend's house recently and his provider is 
> CenturyLink (at home I use TimeWarner Cable). I tried to download
> Tor Tails (over BitTorrent) and the Internet literally dropped so I
> closed BitTorrrent, afterwards I launched the Tor Browser Bundle
> and then my computer was disconnected from the router and couldn't
> reconnect and no one at the house could access the Internet, we had
> to reboot the router to fix the issue. I then enabled Pluggable
> Transports (meet-google or something like that) and now I'm able to
> connect to Tor without any issues. This really concerns me as I was
> able to repeat the crash by launching Tor Browser Bundle and crash
> the router again.
> 
> This worries me as I can see a direct link (Launch Tor Browsre
> Bundle without Pluggable Transports) and (Router and Internet
> require Reboot). Could this be a form of censorship within the
> United States?
> 
> I will be returning home today but this is really worrying me as
> it could be a form of censorship within the United States.
> 
> Does anyone have any ideas or thoughts about this?
> 

As I understand the sequence of events:
 1) Use BitTorrent
 2) Connection drops
 3) TBB cannot connect
 4) You restart the router
 5) You started using meek-google; everything is working

My first question is: between steps 4 and 5, did you try using Tor
without meek-google? If so, was it still unable to connect?

Some additional questions: Have you been able to replicate this issue
at all? Have you determined if it is BitTorrent which seems to cause
the connection to drop? Is it only downloading Tails that causes the
issue?

The reason I ask these questions is because I do have experience with
a wireless router that (to the extent I can determine) gets overloaded
by BitTorrent traffic. When this overload happens, the router
essentially stops relaying traffic and seems to drop the Wifi link.
However, the wireless router would continue to broadcast its SSID
(confirmed with airodump-ng), implying that it was still active to
some extent.

As you describe, other people using this router were unable to relay
traffic. Restarting the router would fix the problem.

I should also note that in this case the router is customer-supplied
and is separate from the modem supplied by the ISP.

Hopefully this is less alarming.

Austin

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJUzwTpAAoJED2RB2pS56Tl3n0P/jEEXRfOtMNbUfKyDfwuDl94
eGd4C5s7un1CqhaL7am8uakBBoMeqUliFNgq3/bVVhYcBOqGby5xCWrl2HzDHwzK
XKNFAPF8fZhjct5rNJZGemah/40wm3bREKbtmT/lgBb2HLegUYYTl4W2MhwfC4wi
KOlmA/h1VEgn4IIydAS0EN/b2l9zpABuv10oAXBOtV63j4pkCWk1LZ6AB5j+2/tt
kcVy5WND/3tByV3UGkEijnOe3oIDh5T0bJ7fe/GfxGHyHjF+AWIIR9B72gpJ6DeZ
jXmtMWMhDZNwHs0jDWgk814ua/Ar/dSBBohMQlzRMYCuzXRCz3U8IJAVpt2QZ1lH
87yC9VVy5D+k7n6xT/hnjyYgaPR9IE90h35IT6wxZe55FfqHUCVBeuozOrJZr+98
LM24zUyPVhJIDx1kf8sH0oRp0ZH3bwIlYi0TQTSOOHKT3UZtkNNBz1j7oI5z0OYA
0giMlEwEw1vV7GjB1W5B4f3lI/0gejbIgGaYw28D9pXDiGYse7fuVCDCziJ5VaSy
g06nXv226xJVdWf8Yj5AjhOp2yXGyb6iiJ44ich4vcaDi28FJLluq0P4CwhdlEvs
QxRgkA74vL1FDj3RwIIDKMCW/1Ah6BW4RYfFDfCoMkrTgPRXtGVlHvhNwFAhfLTp
33NaCxKhG+ur1+VjrbKT
=ExY7
-----END PGP SIGNATURE-----
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

