Delivery-Date: Mon, 20 Apr 2015 18:34:10 -0400
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=-1.7 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	RCVD_IN_DNSWL_MED,T_RP_MATCHES_RCVD,URIBL_BLACK autolearn=no 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 9C8E71E0CE9
	for <archiver@seul.org>; Mon, 20 Apr 2015 18:34:07 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 956F93492A;
	Mon, 20 Apr 2015 22:34:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D18FD34913
 for <tor-talk@lists.torproject.org>; Mon, 20 Apr 2015 22:33:58 +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 3Cf8guCJ8HWW for <tor-talk@lists.torproject.org>;
 Mon, 20 Apr 2015 22:33:58 +0000 (UTC)
Received: from mail.openmailbox.org (mail.openmailbox.org [62.4.1.34])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id A5B7234882
 for <tor-talk@lists.torproject.org>; Mon, 20 Apr 2015 22:33:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail.openmailbox.org (Postfix) with ESMTP id 22EBD2E0A1B
 for <tor-talk@lists.torproject.org>; Tue, 21 Apr 2015 00:33:55 +0200 (CEST)
X-Virus-Scanned: amavisd-new at openmailbox.org
Received: from mail.openmailbox.org ([62.4.1.34])
 by localhost (mail.openmailbox.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0DPU8URBYLCV for <tor-talk@lists.torproject.org>;
 Tue, 21 Apr 2015 00:33:50 +0200 (CEST)
Date: Mon, 20 Apr 2015 22:33:43 +0000
From: Alan Hiew <alanhiew@openmailbox.org>
To: tor-talk@lists.torproject.org
Message-ID: <20150420223343.41764f08@openmailbox.org>
In-Reply-To: <552FF074.3050909@sky-ip.org>
References: <20150416165345.3e15baae@openmailbox.org>
 <552FF074.3050909@sky-ip.org>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; i486-pc-linux-gnu)
Mime-Version: 1.0
Subject: Re: [tor-talk] Why obfs4 bridges aren't work in Tails?
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>

Thu, 16 Apr 2015 20:25:08 +0300
s7r <s7r@sky-ip.org>:

> 
> On Debian Wheezy 64bit with Tor 0.2.5.10 and obfs4proxy installed from
> deb.torproject.org/torproject.org obfs4proxy main (via apt-get) 3
> obfs4 bridges out of a total of 31 crashed with no error or warn in
> Tor log.
> 
> /var/log/tor was an empty file
> /var/log/tor/log.1 (log rotation) had in the last lines the regular
> heartbeat notices, with info about total circuits, relayed traffic,
> [... ]
> 
> Simply started the Tor daemon again on these 3 servers and they are up
> and running, no problem. Will keep an eye on this.
> 

I've made some log analisys and (may be) found why obfs4 bridges don't
work correctly.

I've used tcpdump created by that command:

sudo tcpdump ip -n -nn -x | tee tcpdump.txt

and Tor log file located at /var/log/tor/log


The possible reason is IP-packet fragmentation. I
suspect that obfs4-protocol require sending big packet (with "no
fragmentation" flag/option) and router of my local network and(or)
other routers on the connection way can not pass these packets. My
routers answer: "unreachable - need to frag (mtu 1456)". And in Tor
log:


[info] smartlist_choose_node_by_bandwidth(): Empty routerlist passed in to old node selection for rule weight as guard
[info] should_delay_dir_fetches(): Delaying dir fetches (no running bridges known)
[info] compute_weighted_bandwidths(): Empty routerlist passed in to consensus weight node selection for rule weight
as guard

many times.

obfs3, obfs2 and bridges without pluggable transport all are working
correctly.

WBR, Alan Hiew
-- 
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

