Delivery-Date: Tue, 03 Feb 2015 07:49:49 -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 051491E0A51
	for <archiver@seul.org>; Tue,  3 Feb 2015 07:49:48 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4ED5633820;
	Tue,  3 Feb 2015 12:49:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 253C133816
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 12:49:41 +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 W4hAcwH2nHci for <tor-talk@lists.torproject.org>;
 Tue,  3 Feb 2015 12:49:41 +0000 (UTC)
Received: from nl2.altushost.com (unknown [37.46.125.234])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id EBDB033814
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 12:49:40 +0000 (UTC)
Received: from localhost ([::1]:45425 helo=nl2.altushost.com)
 by nl2.altushost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256)
 (Exim 4.82) (envelope-from <nathaniel@moltennetworks.co.uk>)
 id 1YIcvA-0000TC-PO
 for tor-talk@lists.torproject.org; Tue, 03 Feb 2015 07:49:36 -0500
Received: from 174.97.221.84 ([174.97.221.84]) by nl2.altushost.com (Horde
 Framework) with HTTP; Tue, 03 Feb 2015 12:49:36 +0000
Date: Tue, 03 Feb 2015 12:49:36 +0000
Message-ID: <20150203124936.Horde.Km8hYDNKMDIiKpPEk0sDkQ1@nl2.altushost.com>
From: nathaniel@moltennetworks.co.uk
To: tor-talk@lists.torproject.org
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
 <20150201215032.GC12880@localhost> <54CEAFA9.90800@rawbw.com>
In-Reply-To: <54CEAFA9.90800@rawbw.com>
User-Agent: Internet Messaging Program (IMP) H5 (6.1.4)
MIME-Version: 1.0
Content-Disposition: inline
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - nl2.altushost.com
X-AntiAbuse: Original Domain - lists.torproject.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - moltennetworks.co.uk
X-Get-Message-Sender-Via: nl2.altushost.com: authenticated_id:
 nathaniel@moltennetworks.co.uk
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="Yes"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

I waited and switched my laptop back to Debian Linux from Windows 8.1  
and build my WiFi Driver from source. (it was a Microsoft Driver for  
the Edimax Nano Wifi) (the source was from edimax) and afterwards I  
was able to connect to Tor without crashing the entire WiFi Network. I  
wonder if Microsoft's Driver was tapped or something. I agree the US  
is not as safe as it used to be.


Quoting Yuri <yuri@rawbw.com>:

> On 02/01/2015 13:50, Matthew Finkel wrote:
>> 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].
>
> I didn't get the OP's e-mail, but (assuming this is in US) customers  
> have a lot of leverage. Just keep tor and torrent clients running,  
> and call their customer service, and demand an explanation why the  
> service they charge you money for doesn't work. Let them send the  
> live technician to fix the problem. Escalate this as much as  
> possible. Eventually they will have to fix your connection (with the  
> mentioned services running). And if they don't, you can sue them in  
> small claims court and demand compensation for all time, effort,  
> suffering, emotional distress, deprivation of service, etc, etc,  
> etc. And you will likely easily win the case.
>
> Just trying to work around the problem in technical ways with  
> bridges, Pluggable Transport, trying to hide tor traffic isn't  
> necessarily the right way to deal with the problem.
>
> Yuri
> -- 
> 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



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

