Delivery-Date: Sun, 01 Feb 2015 16:51:01 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	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 1BEAC1E0113
	for <archiver@seul.org>; Sun,  1 Feb 2015 16:50:59 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0601933229;
	Sun,  1 Feb 2015 21:50:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9FB6B32FC6
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 21:50:52 +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 6_EmdFat5_pQ for <tor-talk@lists.torproject.org>;
 Sun,  1 Feb 2015 21:50:52 +0000 (UTC)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com
 [IPv6:2a00:1450:4010:c03::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 4382133222
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 21:50:52 +0000 (UTC)
Received: by mail-la0-f53.google.com with SMTP id gq15so35369023lab.12
 for <tor-talk@lists.torproject.org>; Sun, 01 Feb 2015 13:50:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=from:date:to:subject:message-id:references:mime-version
 :content-type:content-disposition:in-reply-to:user-agent;
 bh=ptgqD7vOD2esEXrUJFeqrjcoWEL6+xL6J8LClgLqUEk=;
 b=HXqfPPjWo3NWWfcHBHOTDlS2AD1FY+cy+o6rAmAHVhOIFCXQgbvVSeHhEc/LE2gar4
 YgmWtlpei4OUsq1E8y+RuohaSlWymqRMfKh5aR9gk6VN9+mHyL7qR94PvjIeF5i+JPR0
 wQmzeWkjj/aKMHWvjuvSNOzucsrhpisAuyiP17XM2FPTXDP6BtaAM5O0Kir/C8BoneZv
 W2WHHGszrfLcGZpYGzZJx/wZFSHsMKXPfmQT4Ug94cvcWpoLfbYtMPk5f5mjIXorTS5s
 C39diE1SC3qokiXOZZQOaqxG4jXnuRzZfTD0k5VNYU9XO0bbxJBWahAxxxsvtZXp+zc/
 UhCg==
X-Received: by 10.152.21.228 with SMTP id y4mr16893488lae.72.1422827449117;
 Sun, 01 Feb 2015 13:50:49 -0800 (PST)
Received: from localhost (assk2.torservers.net. [78.108.63.44])
 by mx.google.com with ESMTPSA id mq3sm4023107lbb.31.2015.02.01.13.50.46
 for <tor-talk@lists.torproject.org>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Sun, 01 Feb 2015 13:50:48 -0800 (PST)
From: Matthew Finkel <matthew.finkel@gmail.com>
X-Google-Original-From: Matthew Finkel <Matthew.Finkel@gmail.com>
Date: Sun, 1 Feb 2015 21:50:35 +0000
To: tor-talk@lists.torproject.org
Message-ID: <20150201215032.GC12880@localhost>
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
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>

On Sun, Feb 01, 2015 at 04:14:26PM +0000, nathaniel@moltennetworks.co.uk wrote:
> 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.
> 

Wow. That is quite coincidence. Can you ask your friend to contact
CenturyLink and ask them why this happened. It appears no one has
experienced this or, at least, no one updated the Good/Bad ISP wiki
page with this[0].

You probably chose the meek-google pluggable transport[1]. Basically,
it takes advantage of the fact that someone can run a webserver on
Google's infrastructure (using AppEngine) such that when you establish
a HTTPS session with the webserver, your ISP only see the connection
to Google's servers and not the specific server you're connecting to;
the specific webserver (meek) is defined within the encrypted portion.
When Google receives the connection, it correctly passes the
connection to the meek webserver. From there, the webserver then sends
your connection to a Tor Bridge, which is your first hop into the Tor
network. It's a very cool idea and it seems to work very well. The
current Tor Browser also supports connecting to a meek instance running
on Amazon's EC2 infrastructure and on Microsoft's Azure infrastructure.

[0] https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs
[1] https://trac.torproject.org/projects/tor/wiki/doc/meek#Overview

> 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?
> 

Sounds like it. It would be great if someone directly asks CenturyLink
about this.
> 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?

It's interesting that resetting the modem allowed you to access the
internet again. I wonder if the internet connection block you
experienced was based on the modem's IP address, and when you reset
the modem it was given a new dynamic IP address - hence bypassing the
block. This reminds me a little of the way China handles connections[2],
but it's still a little early to make a serious comparison.

The more information we can get about this, the better.

[2] https://blog.torproject.org/blog/closer-look-great-firewall-china


Also, as a general aside, please remember that trying to run a
bittorrent client over Tor is a bad idea[3] (the first half is the
relevant portion). I'm not sure if this was the intention, but just a
a friendly reminder :)

[3] https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea
-- 
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

