Delivery-Date: Sun, 01 Feb 2015 19:45:35 -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 046811E070D
	for <archiver@seul.org>; Sun,  1 Feb 2015 19:45:33 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3B28C3332C;
	Mon,  2 Feb 2015 00:45:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 84E71332E6
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:45:26 +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 ECOLlWu5PlTa for <tor-talk@lists.torproject.org>;
 Mon,  2 Feb 2015 00:45:26 +0000 (UTC)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com
 [IPv6:2a00:1450:400c:c03::229])
 (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 11E1633282
 for <tor-talk@lists.torproject.org>; Mon,  2 Feb 2015 00:45:26 +0000 (UTC)
Received: by mail-we0-f169.google.com with SMTP id u56so36265391wes.0
 for <tor-talk@lists.torproject.org>; Sun, 01 Feb 2015 16:45:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=Jx+JL4UWi2VJAQC5cExzwbtxlhZl+V47+J8DQzhmk1c=;
 b=fRH0I57LK/F7J9GIkICxMnzDvIlj6TeD7RxF0PKmPzRh+h4UejwrsmHYIwqkLw4GiL
 rPahzevwD3Tx5kY7TmUYkKnlkZ61VdxTREdz5nBKhKCKIrq/uwg7CsgYbr6IPb4rvI9R
 ZUZGUxOu0OLHm6PhoawRwZATcxiC768x25+9/mnA/55YJEvDVsENzfSHYZjO0K0scaq1
 NIF1RFXRoOGSAJ8GfFXMQhbh8g29Uzqa2/bDo1mL/fiLoScVJGHkIurL7BAglt7TCkf1
 IbLhkICiAVOrMaMvnvkaspkyY62umT+5GhM5onknxQGxNPfH/akR0jrFgFIPfmg0mMF6
 AJGg==
MIME-Version: 1.0
X-Received: by 10.194.104.196 with SMTP id gg4mr36732980wjb.31.1422837923208; 
 Sun, 01 Feb 2015 16:45:23 -0800 (PST)
Received: by 10.27.101.198 with HTTP; Sun, 1 Feb 2015 16:45:23 -0800 (PST)
In-Reply-To: <CAKrUFkgbwt8PtKhY_CVvQtWq0oYKHJOhFReK+Kx5nZd8nsj4Aw@mail.gmail.com>
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
 <20150201215032.GC12880@localhost> <54CEAFA9.90800@rawbw.com>
 <CABMkiz5q74RTZLzpoSXew3ZgyJbB2wkAXw8KFoAQ2XyNPStk6A@mail.gmail.com>
 <54CEBA1C.2010206@rawbw.com>
 <CABMkiz5HH5RXp0+QLDmoxOej_5OZrYUheBpHURaEe_S2oXc-nQ@mail.gmail.com>
 <CAKrUFkgbwt8PtKhY_CVvQtWq0oYKHJOhFReK+Kx5nZd8nsj4Aw@mail.gmail.com>
Date: Sun, 1 Feb 2015 17:45:23 -0700
Message-ID: <CAKrUFkj0i2gf_3-LWucpAD+9YZ5Ly-3s0Uf9ophc5+eEW3iLCw@mail.gmail.com>
From: Max Bond <max.o.bond@gmail.com>
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>

Oops, typo.

What I meant to say was I scanned about twenty-five thousand hosts for
Heartbleed.

On Sun, Feb 1, 2015 at 5:43 PM, Max Bond <max.o.bond@gmail.com> wrote:

> Hello,
>
> I've been using CenturyLink for ADSL in the US for five or six years
> (coincidentally this is my last day with them, so I probably won't be able
> to do much testing), and I have never had a problem using Tor; as soon as I
> saw this thread, I fired up Tor Browser and accessed a few websites. I
> didn't use pluggable transports and everything went smoothly.
>
> I can confirm that restarting the router changes the IP address, and that
> they have some level of remote management (I've noticed them installing
> firmware updates to my router.)
>
> I've never heard of this "protection program" but I doubt its the cause.
> I've never known it to be zealous, let alone overzealous; I scanned about
> twenty-five thousand, multiple times, to gather statistics. I never heard a
> peep out of
> them. I imagine that they'd watch for large volumes of obvious attack
> traffic before they targeted Tor, from a malware perspective.
>
> All that being said, perhaps this is a regional difference.
>
> Hope that helps,
> Max
>
>
> On Sun, Feb 1, 2015 at 4:59 PM, Ben Tasker <ben@bentasker.co.uk> wrote:
>
>> > 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
>>
>
>
-- 
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

