inet6 addr: 2607:5500:2000:5d3::de95/64 Scope:Global UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:3169513589 errors:0 dropped:0 overruns:0 frame:0 TX packets:3438384506 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2825471195234 (2.5 TiB) TX bytes:2911672053962 (2.6 TiB)
looks like a IPv6 to me. Will contact Hostwinds anyway, I hate them with every cell of my body. Thank you Tim.
niftybunny
abuse@to-surf-and-protect.net
On 24 Jan 2017, at 04:25, teor teor2345@gmail.com wrote:
On 24 Jan 2017, at 14:18, niftybunny abuse@to-surf-and-protect.net wrote: ... Connecting to dist.torproject.org (dist.torproject.org)|2a01:4f8:211:6e8:0:823:2:1|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|38.229.72.16|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 5534005 (5.3M) [application/x-gzip] Saving to: 'tor-0.2.9.9.tar.gz'
tor-0.2.9.9.tar.gz 100%[===================================================================================================================>] 5.28M 9.89MB/s in 0.5s
2017-01-23 22:12:41 (9.89 MB/s) - 'tor-0.2.9.9.tar.gz' saved [5534005/5534005]
Is this normal behaviour?
niftybunny abuse@to-surf-and-protect.net
It appears that your DNS returns (and apparently prefers) IPv6 addresses, but your host lacks IPv6 connectivity.
If you were connecting over Tor, you would see similar behaviour with a DNS name that only resolves to an IPv6 address (like ipv6.google.com), because only ~15% of exits support IPv6.
And if you don't set the IPv6Traffic on the SOCKSPort, you will never connect to a remote IPv6 address.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays