Delivery-Date: Tue, 12 Aug 2014 04:32:16 -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=-4.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY
	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 B70581E0A40;
	Tue, 12 Aug 2014 04:32:14 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7EAB330754;
	Tue, 12 Aug 2014 08:32:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DF80A30348
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 08:32:06 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 yiYp5N2Od8YV for <tor-talk@lists.torproject.org>;
 Tue, 12 Aug 2014 08:32:06 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id B7566301FD
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 08:32:06 +0000 (UTC)
Received: from plantcutter.riseup.net (unknown [10.0.1.121])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net", Issuer "Gandi Standard SSL CA" (not verified))
 by mx1.riseup.net (Postfix) with ESMTPS id 7232650EF4
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 01:32:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1407832323; bh=+jVvfKcEc3IcmQZT9pYTK3uE7vCc5b+1eMlSDPcxoAo=;
 h=From:To:Subject:In-Reply-To:References:Date:From;
 b=XMrN1K0zX4kM+L0LlfY6i+Ymt8R1A0xLg1h5x0bEeAjLhZr9lyp+izFakMr3wlaIr
 uGsbmWsh6PKk0FHy+6DhXrdXRIDJyNqvljZxrhbx6SyxveFBbQkHvxxnrcxJ/yHSlR
 nCjYCUkROPvpg40mz3TzaNE0yO8ZN+jRYjYmOKQo=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: desnacked) with ESMTPSA id 97B4C22116
From: George Kadianakis <desnacked@riseup.net>
To: tor-talk@lists.torproject.org
In-Reply-To: <CAKMgAkSgH_3SR=z80is6RxUR=FVdvdYEDzxDn_MOPyzkyyGVXQ@mail.gmail.com>
 (saurav dahal's message of "Tue, 12 Aug 2014 11:27:28 +0900")
References: <CAKMgAkSgH_3SR=z80is6RxUR=FVdvdYEDzxDn_MOPyzkyyGVXQ@mail.gmail.com>
User-Agent: Microsoft Outlook Express 6.00.2900.5843
Date: Tue, 12 Aug 2014 11:32:22 +0300
Message-ID: <87ppg6152h.fsf@riseup.net>
MIME-Version: 1.0
X-Virus-Scanned: clamav-milter 0.98.1 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] About bandwidth weights selection
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>

saurav dahal <dahal.saurav@gmail.com> writes:

> Hello,
>
> While choosing a possible guard, a client multiplies Wgg with the bandwidth
> weight of a possible relay having guard flag.
>
> But if a client wants to choose a relay, for guard position, having both
> Guard and Exit flag (EE), then will it multiply bandwidth weight with Wgg
> or Wgd?
>

If it's a Guard+Exit, it will multiply the bandwidth weight with Wgd:
Wgd - Weight for Guard+Exit-flagged nodes in the guard Position
-- 
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

