Delivery-Date: Sun, 01 Feb 2015 18:59:45 -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 CC9C11E04FE
	for <archiver@seul.org>; Sun,  1 Feb 2015 18:59:42 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 66530332DF;
	Sun,  1 Feb 2015 23:59:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 15BB133272
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 23:59:35 +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 oFLhIrEXkMZd for <tor-talk@lists.torproject.org>;
 Sun,  1 Feb 2015 23:59:35 +0000 (UTC)
Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com
 [209.85.218.45])
 (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 DCF653323D
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 23:59:34 +0000 (UTC)
Received: by mail-oi0-f45.google.com with SMTP id g201so41945905oib.4
 for <tor-talk@lists.torproject.org>; Sun, 01 Feb 2015 15:59:32 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:content-type;
 bh=YqYf3qRI2PxYf+z+wTn2K98mcjoSiZw1VCFfZTi+7c0=;
 b=crRqyQHJgjpUZd9611kATGoD+Be1KpcUVAA1GhT1O7X7AFEHXH7kEwGFaitxZGarXS
 VH0hfIZvcN8wULtfl9V19HRBqy6V6I6yITZ0+zfFeutBY3Va9y2f8jm3jBcjNo/JYGWA
 4vkg8cXs8WuDDRd75oLIQ622zTBvX1xVGxjDAM15kdOdX5Uk1dqH9Ojon72JCNG3txzK
 pJMyDSnfGm2+B1Or+/ohekfo6g327YdR2zplL4pmMz/ycGTNKZWwynMhH0owW++/pMVy
 ddHNLIV7lS/2Lp6xr66vLDZO0g4YOfS5E+8lenzYixfrGRnsiwnxrR+dx7dOU9TWZgPU
 iNuA==
X-Gm-Message-State: ALoCoQm2gSGN7RzksQbjgb6aY4H1+2l/ygwRoUqpqjYHUVOFy/+u8lhOIEZhzTfc4xczOqms78dK
MIME-Version: 1.0
X-Received: by 10.202.77.13 with SMTP id a13mr9740208oib.49.1422835172409;
 Sun, 01 Feb 2015 15:59:32 -0800 (PST)
Received: by 10.76.24.136 with HTTP; Sun, 1 Feb 2015 15:59:32 -0800 (PST)
X-Originating-IP: [81.134.152.4]
In-Reply-To: <54CEBA1C.2010206@rawbw.com>
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
 <20150201215032.GC12880@localhost> <54CEAFA9.90800@rawbw.com>
 <CABMkiz5q74RTZLzpoSXew3ZgyJbB2wkAXw8KFoAQ2XyNPStk6A@mail.gmail.com>
 <54CEBA1C.2010206@rawbw.com>
Date: Sun, 1 Feb 2015 23:59:32 +0000
Message-ID: <CABMkiz5HH5RXp0+QLDmoxOej_5OZrYUheBpHURaEe_S2oXc-nQ@mail.gmail.com>
From: Ben Tasker <ben@bentasker.co.uk>
To: tor-talk@lists.torproject.org
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>

> 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 it has been known for some infections to establish a connection back to
their C&C via Tor, it's not inconceivable an ISP (or more likely,
who-ever's providing their kit) might apply a policy which could
(deliberately or otherwise) wind up blocking Tor. Whether Tor is malware
has no real bearing, what matters is whether it's traffic is perceived as
such by the ISP

I missed the part about the torrent client, though it sounds like the
behaviour was slightly different. In either case though, the OP's
description makes it sound like the external connection dropped in it's
entirety - for any kind of filtering/blocking that's massive overkill. If
you were being restricted to a walled garden, outside connectivity might
appear unavailable unless you were going to a whitelisted IP.

On my (UK) ISP, a reboot of the router pretty much guarantees a new IP,
though I have also been with providers where that wasn't the case.

On Sun, Feb 1, 2015 at 11:43 PM, Yuri <yuri@rawbw.com> wrote:

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



-- 
Ben Tasker
https://www.bentasker.co.uk
-- 
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

