-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I opened my exit for IPv6 after Moritz encouraged us to do so here at this list.
I do observe a traffic of 1-2 GB. for IPv6, IPv4 is always abound 300 GB/day. The exit is configure for 8 MB/sec throughgput (==20 TB/month). I do wonder, what are expected values for IPv6.
Furthermore between 11th of August and 25th of September I observed a traffic of about 30-40 GB per day for IPv6 - but why only in this time frame ?
- -- Toralf, pgp: C4EACDDE 0076E94E
On 13 Dec 2015, at 02:52, Toralf Förster toralf.foerster@gmx.de wrote:
Signed PGP part I opened my exit for IPv6 after Moritz encouraged us to do so here at this list.
I do observe a traffic of 1-2 GB. for IPv6, IPv4 is always abound 300 GB/day. The exit is configure for 8 MB/sec throughgput (==20 TB/month). I do wonder, what are expected values for IPv6.
Furthermore between 11th of August and 25th of September I observed a traffic of about 30-40 GB per day for IPv6 - but why only in this time frame ?
Tor Browser 5.0.4 has its SOCKSPort configured with "IPv6Traffic PreferIPv6". This means that if your DNS resolver returns IPv6 records, Tor Browser and your Exit should default to using IPv6 to websites that have both an IPv4 and IPv6 address.
Is your DNS resolver correctly returning AAAA records along with A records for all sites that have them? (If it's only returning AAAA records for a few sites, or for IPv6-only sites, that could be your problem.)
As far as I know, nothing changed in Tor Browser that could cause a dramatic IPv6 traffic drop-off.
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 12/12/2015 07:39 PM, Tim Wilson-Brown - teor wrote:
Is your DNS resolver correctly returning AAAA records along with A records for all sites that have them?
Ah - good hint. The commands 'nslookup' and 'host' works fine AFAICS. Nevertheless I made a changed at resolv.conf put the 3 IPv6 DNS server lines above of those of IPv4 (I'm using dnsmasq) :
$> cat /etc/resolv.conf # Generated by net-scripts for interface enp3s0 domain your-server.de nameserver 127.0.0.1 nameserver 2a01:4f8:0:a0a1::add:1010 nameserver 2a01:4f8:0:a102::add:9999 nameserver 2a01:4f8:0:a111::add:9898 nameserver 213.133.98.98 nameserver 213.133.99.99 nameserver 213.133.100.100
Will see, if this makes a difference.
- -- Toralf, pgp: C4EACDDE 0076E94E
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/20/2015 06:06 PM, Toralf Förster wrote:
t. The commands 'nslookup' and 'host' works fine
correction:
tor-relay ~ # host -t AAAA google.com google.com has IPv6 address 2a00:1450:4001:800::1003
tor-relay ~ # host -t AAAA google.com google.com has no AAAA record
:-(
- -- Toralf, pgp: C4EACDDE 0076E94E
tor-relays@lists.torproject.org
-
Tim Wilson-Brown - teor -
Toralf Förster