Delivery-Date: Sun, 01 Feb 2015 18:43:36 -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 8B20B1E04FE
	for <archiver@seul.org>; Sun,  1 Feb 2015 18:43:34 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 96EA633279;
	Sun,  1 Feb 2015 23:43:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C23BC33204
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 23:43:27 +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 kLxuYveyyAvA for <tor-talk@lists.torproject.org>;
 Sun,  1 Feb 2015 23:43:27 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by eugeni.torproject.org (Postfix) with ESMTP id 9763233200
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 23:43:27 +0000 (UTC)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t11NhP5S075450
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <tor-talk@lists.torproject.org>; Sun, 1 Feb 2015 15:43:25 -0800 (PST)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Message-ID: <54CEBA1C.2010206@rawbw.com>
Date: Sun, 01 Feb 2015 15:43:24 -0800
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
 <20150201215032.GC12880@localhost> <54CEAFA9.90800@rawbw.com>
 <CABMkiz5q74RTZLzpoSXew3ZgyJbB2wkAXw8KFoAQ2XyNPStk6A@mail.gmail.com>
In-Reply-To: <CABMkiz5q74RTZLzpoSXew3ZgyJbB2wkAXw8KFoAQ2XyNPStk6A@mail.gmail.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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 02/01/2015 15:24, Ben Tasker wrote:
> Looking at their info page -
> http://www.centurylink.com/Pages/AboutUs/Legal/InternetServiceManagement/  -
> it seems Century Link run what they call a Protection Program.
>
> If they detect (what they consider to be) potentially malicious traffic,
> the connection gets put in a walled garden to notify the end user.

This policy document talks about botnet and virus infections, so it 
doesn't seem relevant to OP's friend, because tor and torrent clients 
are neither.

> As others have said, rebooting the router would likely have acquired a new
> IP, so effectively cancelling a block.

Not familiar with CenturyLink, but with Comcast digital cable only 
rebooting with changed client MAC address would cause an IP change. 
Otherwise IP is very persistent.

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

