Delivery-Date: Sun, 01 Feb 2015 18:25:11 -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 B209E1E04FE
	for <archiver@seul.org>; Sun,  1 Feb 2015 18:25:09 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DFDB8332DA;
	Sun,  1 Feb 2015 23:25:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BA6E1332D8
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 23:25:01 +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 LKmVm3cf3zNb for <tor-talk@lists.torproject.org>;
 Sun,  1 Feb 2015 23:25:01 +0000 (UTC)
Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com
 [209.85.214.170])
 (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 97474332D2
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 23:25:01 +0000 (UTC)
Received: by mail-ob0-f170.google.com with SMTP id va2so2395217obc.1
 for <tor-talk@lists.torproject.org>; Sun, 01 Feb 2015 15:24:59 -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=3ha7xLF/yE/mSC+qOkOqwBIzQXFDcB5Q6UKPg4yIf+8=;
 b=EHzRiVG6DHuBC4hf5wCTevyac8huK8RiW1Z8aSZvLWyc7GTHGLxPBVdREkFSG5hFO/
 J3Dl+r2AT/yVlLnuxcmmPa1ceGZ0FjEZkR94m76HXJ62a911az1gDcJhILQHKzLjUOWj
 YqTJ1Fz8zUtMtNxsInla4FEAdC6oEjgBjsr65ocZ7OiN1mt6NsXjxEVjWuiZfju7a8oh
 7tkqvlvICEZHzdvImLz4ugK+Ea8uaBTcbmeb8pBQnTLH6kCTwFYlpQJZUOCcacH1ycRS
 ++8u8lYxybqelfYU3HyQwBy2QMG43S4n0wwIOSvzqsLHkPm0iHYIYRvlgWg/FYWyekTz
 YqHw==
X-Gm-Message-State: ALoCoQlVDoFFYL9b+KQiEHNYfKiORKbzxpqej3fS4JHRFfUMLNqE1/8+nMSwKWLSXrI2SgT1u545
MIME-Version: 1.0
X-Received: by 10.202.97.130 with SMTP id v124mr9852734oib.34.1422833099008;
 Sun, 01 Feb 2015 15:24:59 -0800 (PST)
Received: by 10.76.24.136 with HTTP; Sun, 1 Feb 2015 15:24:58 -0800 (PST)
X-Originating-IP: [81.134.152.4]
In-Reply-To: <54CEAFA9.90800@rawbw.com>
References: <20150201161426.Horde.hZSAupwu-wI7NiSrsdcVoQ1@nl2.altushost.com>
 <20150201215032.GC12880@localhost> <54CEAFA9.90800@rawbw.com>
Date: Sun, 1 Feb 2015 23:24:58 +0000
Message-ID: <CABMkiz5q74RTZLzpoSXew3ZgyJbB2wkAXw8KFoAQ2XyNPStk6A@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>

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.

Is the OP's friend using non-Century link DNS? Wondering if it could be as
simple as an over-enthusiastic detection policy triggering the walled
garden. I've no idea how Century Link achieve redirecting to the
notification page, but if they simply return the IP of one of their
servers, using external DNS servers could easily break that leading to the
impression that your internet has dropped out.

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



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

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



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

