-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Looking at the daily traffic stats got from my ISP I had an Incoming of 50 GB/day and Outgoing of 1.6 GB with version 0.2.6.10 whereas the -rc now gives 8 GB Incoming and 0.06 Outgoing.
Anybody with similar experiences ?
- -- Toralf, pgp key: 872AE508 0076E94E
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 28 Sep 2015 21:03:02 +0200 Toralf Förster toralf.foerster@gmx.de wrote:
Looking at the daily traffic stats got from my ISP I had an Incoming of 50 GB/day and Outgoing of 1.6 GB with version 0.2.6.10 whereas the -rc now gives 8 GB Incoming and 0.06 Outgoing.
Anybody with similar experiences ?
You forgot to mention what IPv6 has to do with any of this, i.e. why do you think that this difference is specifically IPv6-related.
- -- With respect, Roman
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 09/28/2015 09:07 PM, Roman Mamedov wrote:
You forgot to mention what IPv6 has to do with any of this, i.e. why do you think that this difference is specifically IPv6-related.
My exit relay F1BE15429B3CE696D6807F4D4A58B1BFEC45C822 has an overall traffic of about 150 GB/day.
Few weeks ago I added IPv6 to the exit policy too. Since that time I observed the mentioned IPv6 traffic.
With the new Tor version I realized the decrease.
I verified that switching back to 0.2.6.10 gives about 200 IPv6 connections to other relays, whereas w/ 0.2.7.3-rc I do just have 1 IPv6 connection to tor.noreply.org.
- -- Toralf, pgp key: 872AE508 0076E94E
On Mon, 28 Sep 2015, Toralf Förster wrote:
I verified that switching back to 0.2.6.10 gives about 200 IPv6 connections to other relays, whereas w/ 0.2.7.3-rc I do just have 1 IPv6 connection to tor.noreply.org.
Could this be something related to https://trac.torproject.org/projects/tor/ticket/17149 ?
~Saper
On 28 Sep 2015, at 22:53, Marcin Cieslak saper@saper.info wrote:
On Mon, 28 Sep 2015, Toralf Förster wrote:
I verified that switching back to 0.2.6.10 gives about 200 IPv6 connections to other relays, whereas w/ 0.2.7.3-rc I do just have 1 IPv6 connection to tor.noreply.org.
Could this be something related to https://trac.torproject.org/projects/tor/ticket/17149 https://trac.torproject.org/projects/tor/ticket/17149
Yes, that bug will most likely discard/delete your entire exit policy, and cause torrc parsing to fail.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP 968F094B
teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 09/28/2015 10:53 PM, Marcin Cieslak wrote:
Could this be something related to https://trac.torproject.org/projects/tor/ticket/17149 ?
The version I run here is already fixed (that issue was in a pre-release of 0.2.7.3-rc - I'm the bug reporter).
- -- Toralf, pgp key: 872AE508 0076E94E
tor-relays@lists.torproject.org
-
Marcin Cieslak -
Roman Mamedov -
Tim Wilson-Brown - teor -
Toralf Förster