Delivery-Date: Sun, 01 Feb 2015 17:16:57 -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,FREEMAIL_FROM,
	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 1DC2A1E034D
	for <archiver@seul.org>; Sun,  1 Feb 2015 17:16:56 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 79118332B4;
	Sun,  1 Feb 2015 22:16:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D3C973319E
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 22:16:50 +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 owk1JpimlU7T for <tor-talk@lists.torproject.org>;
 Sun,  1 Feb 2015 22:16:50 +0000 (UTC)
Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.200])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "Self-signed" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id A6CC033071
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 22:16:50 +0000 (UTC)
Received: from smtp3.hushmail.com (localhost [127.0.0.1])
 by smtp3.hushmail.com (Postfix) with SMTP id 05019E0190
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 22:16:48 +0000 (UTC)
Received: from smtp.hushmail.com (w3.hushmail.com [65.39.178.62])
 by smtp3.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 22:16:47 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id D6A01C03CC; Sun,  1 Feb 2015 22:16:47 +0000 (UTC)
MIME-Version: 1.0
Date: Sun, 01 Feb 2015 17:16:47 -0500
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
Message-Id: <20150201221647.D6A01C03CC@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.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>


nathaniel@moltennetworks.co.uk wrote:
[...] 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.

Did you try without using PT? Does this problem with connecting to Tor
directly also occur if you connect to a bridge directly. If they're
blocking Tor they should figure out the bridge is being used to access
Tor and you will shortly experience an offline/non-connectable bridge
or modem/router problem. It's also interesting you say you were
disconnected from the *router* -- what about everyone else. You might
be able to disable remote admin of router settings but that won't stop
them from resetting the device altogether (which might have the
symptom of appearing to be disconnected from the router).

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

