Delivery-Date: Sun, 29 Nov 2015 10:10:59 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	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 757AE1E08D6;
	Sun, 29 Nov 2015 10:10:57 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5DCF137FF7;
	Sun, 29 Nov 2015 15:10:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E3D7437FEA
 for <tor-talk@lists.torproject.org>; Sun, 29 Nov 2015 15:10:47 +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 jEhzNUcGo-M4 for <tor-talk@lists.torproject.org>;
 Sun, 29 Nov 2015 15:10:47 +0000 (UTC)
Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com
 [IPv6:2607:f8b0:4003:c06::244])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id C626A36782
 for <tor-talk@lists.torproject.org>; Sun, 29 Nov 2015 15:10:44 +0000 (UTC)
Received: by oige206 with SMTP id e206so8713435oig.2
 for <tor-talk@lists.torproject.org>; Sun, 29 Nov 2015 07:10:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:from:date:message-id:subject:to:content-type;
 bh=JQ6CRTUmV8+2rs/QqlWsArWmigBB9tGiUFiXTSUp1Pg=;
 b=A/M+X9SrZcehM80DSeG/WqVrXp3GXWekUF/LASOXUmJF7nX/4WEY9Qo1mOUqWKlrBj
 I/QDmEtYRFOLR3Uavga9TX5cUjAzlmX4Y0dgNXZmfDnKEQPVfdsAwiWxlJVH6w0h900n
 7enBa4eWQwjoa/ooqgSeUR6B1JfdWJKxmgDrWCYs+Yjot3vRcsCx9yhvXPmjRrEn6jPR
 8pozCOo6qMOYyxckgeFfm6kr04I/y6wwOWcA4b6XsJacBN3rIalSHVbLdBIZDyKz6YT5
 urcmqzudfGveJNdn5JDjpmZZgECqblW2REmjY5Ta1N2oQA06g8PHoN0ofMBRRRpeHlae
 UC7w==
X-Received: by 10.202.211.139 with SMTP id k133mr40645873oig.9.1448809531333; 
 Sun, 29 Nov 2015 07:05:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.85.196 with HTTP; Sun, 29 Nov 2015 07:05:12 -0800 (PST)
From: Amin s <asgetlostman@gmail.com>
Date: Sun, 29 Nov 2015 18:35:12 +0330
Message-ID: <CAPrtOHP7CGRmrcsHNc7KtSA2Cm1NJ=Af1i5CMf7y=LN3H5q2_g@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] TOR and Obfsproxy packet size
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>

I have some questions about TOR and Obfsproxy packet size.

   1. TOR cell size is 512 bytes but most TOR packets have size of 586
   bytes [1].

My question is that why there is such difference in size (74 bytes
difference)?

   1. In my own testing, instead of TOR packets with size of 586 bytes,
   there are packets with size of 543 bytes in TOR traffic and packets with
   size of 565 bytes in Obfsproxy traffic.

My question here is that why doesn't TOR or Obfsproxy generate 586 bytes?
the size that reported in lots of papers like link [1] ?

   1. In my own testing on TOR traffic, from 9939 packets that were sent
   from client to server, there were 2648 packets with different sizes than
   543, like 126,1086,1629,4101,612 and so on.

If TOR cell size is fixed, then why are there packets with different sizes
than 543? (why don't all of the packets have the same 543 bytes in size?)

Relating to above question, there are lots of packets with size of 1460
bytes in backward direction (from server to client). So what happens to the
fixed cell size?


[1] http://arxiv.org/pdf/1305.3199.pdf
-- 
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

