xxx@xxxx:~# wget https://www.torproject.org/dist/tor-0.2.9.9.tar.gz converted 'https://www.torproject.org/dist/tor-0.2.9.9.tar.gz' (ANSI_X3.4-1968) -> 'https://www.torproject.org/dist/tor-0.2.9.9.tar.gz' (UTF-8) --2017-01-23 22:12:32-- https://www.torproject.org/dist/tor-0.2.9.9.tar.gz Resolving www.torproject.org (www.torproject.org)... 2620:0:6b0:b:1a1a:0:26e5:4810, 2001:858:2:2:aabb:0:563b:1e28, 2001:41b8:202:deb:213:21ff:fe20:1426, ... Connecting to www.torproject.org (www.torproject.org)|2620:0:6b0:b:1a1a:0:26e5:4810|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|2001:858:2:2:aabb:0:563b:1e28|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|2a01:4f8:172:1b46:0:abba:5:1|:443... failed: Network is unreachable. Connecting to www.torproject.org (www.torproject.org)|82.195.75.101|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://dist.torproject.org/tor-0.2.9.9.tar.gz [following] converted 'https://dist.torproject.org/tor-0.2.9.9.tar.gz' (ANSI_X3.4-1968) -> 'https://dist.torproject.org/tor-0.2.9.9.tar.gz' (UTF-8) --2017-01-23 22:12:36-- https://dist.torproject.org/tor-0.2.9.9.tar.gz Resolving dist.torproject.org (dist.torproject.org)... 2620:0:6b0:b:1a1a:0:26e5:4810, 2001:41b8:202:deb:213:21ff:fe20:1426, 2a01:4f8:172:1b46:0:abba:5:1, ... Connecting to dist.torproject.org (dist.torproject.org)|2620:0:6b0:b:1a1a:0:26e5:4810|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:443... failed: Network is unreachable. Connecting to dist.torproject.org (dist.torproject.org)|2a01:4f8:172:1b46:0:abba:5:1|:443... failed: Network is unreachable. 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
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 ------------------------------------------------------------------------
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
On 24 Jan 2017, at 14:31, niftybunny <abuse@to-surf-and-protect.net> wrote:
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.
$ wget dist.torproject.org --2017-01-24 03:34:08-- http://dist.torproject.org/ Resolving dist.torproject.org (dist.torproject.org)... 2001:41b8:202:deb:213:21ff:fe20:1426, 2620:0:6b0:b:1a1a:0:26e5:4810, 2a01:4f8:172:1b46:0:abba:5:1, ... Connecting to dist.torproject.org (dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:80... connected. HTTP request sent, awaiting response... 302 Found ... dist.torproject.org works over IPv6 via a US Hurricane Electric tunnel, and from OVH in France and Canada, so I'd check with your provider. 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 ------------------------------------------------------------------------
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation...
On Jan 23, 2017, at 21:38, teor <teor2345@gmail.com> wrote:
On 24 Jan 2017, at 14:31, niftybunny <abuse@to-surf-and-protect.net> wrote:
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.
$ wget dist.torproject.org --2017-01-24 03:34:08-- http://dist.torproject.org/ Resolving dist.torproject.org (dist.torproject.org)... 2001:41b8:202:deb:213:21ff:fe20:1426, 2620:0:6b0:b:1a1a:0:26e5:4810, 2a01:4f8:172:1b46:0:abba:5:1, ... Connecting to dist.torproject.org (dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:80... connected. HTTP request sent, awaiting response... 302 Found ...
dist.torproject.org works over IPv6 via a US Hurricane Electric tunnel, and from OVH in France and Canada, so I'd check with your provider.
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
Could I get an ELI5 for this please? niftybunny abuse@to-surf-and-protect.net
On 24 Jan 2017, at 04:40, John Ricketts <john@quintex.com> wrote:
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation...
On 24 Jan 2017, at 15:18, niftybunny <abuse@to-surf-and-protect.net> wrote:
Could I get an ELI5 for this please?
If you want an ELI5, explain your request like I'm five years old.
On 24 Jan 2017, at 04:40, John Ricketts <john@quintex.com> wrote:
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation…
When two big internet companies don't agree on who pays when they swap packets, they punish their users by refusing to swap packets with each other. 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 ------------------------------------------------------------------------
This may help. https://lists.gt.net/nanog/users/187011 On Jan 23, 2017, at 22:24, teor <teor2345@gmail.com<mailto:teor2345@gmail.com>> wrote: On 24 Jan 2017, at 15:18, niftybunny <abuse@to-surf-and-protect.net<mailto:abuse@to-surf-and-protect.net>> wrote: Could I get an ELI5 for this please? If you want an ELI5, explain your request like I'm five years old. On 24 Jan 2017, at 04:40, John Ricketts <john@quintex.com<mailto:john@quintex.com>> wrote: It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation... When two big internet companies don't agree on who pays when they swap packets, they punish their users by refusing to swap packets with each other. 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<mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
BGP should choose another path? BGP Routing is highly “political” but IPs just black holed is really really bad … If this is true: WTF?! niftybunny abuse@to-surf-and-protect.net
On 24 Jan 2017, at 05:24, teor <teor2345@gmail.com> wrote:
On 24 Jan 2017, at 15:18, niftybunny <abuse@to-surf-and-protect.net> wrote:
Could I get an ELI5 for this please?
If you want an ELI5, explain your request like I'm five years old.
On 24 Jan 2017, at 04:40, John Ricketts <john@quintex.com> wrote:
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation…
When two big internet companies don't agree on who pays when they swap packets, they punish their users by refusing to swap packets with each other.
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
I am forced to peer with both Cogent and HE because of this. On Jan 23, 2017, at 22:28, niftybunny <abuse@to-surf-and-protect.net<mailto:abuse@to-surf-and-protect.net>> wrote: BGP should choose another path? BGP Routing is highly "political" but IPs just black holed is really really bad ... If this is true: WTF?! niftybunny abuse@to-surf-and-protect.net<mailto:abuse@to-surf-and-protect.net> On 24 Jan 2017, at 05:24, teor <teor2345@gmail.com<mailto:teor2345@gmail.com>> wrote: On 24 Jan 2017, at 15:18, niftybunny <abuse@to-surf-and-protect.net<mailto:abuse@to-surf-and-protect.net>> wrote: Could I get an ELI5 for this please? If you want an ELI5, explain your request like I'm five years old. On 24 Jan 2017, at 04:40, John Ricketts <john@quintex.com<mailto:john@quintex.com>> wrote: It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation... When two big internet companies don't agree on who pays when they swap packets, they punish their users by refusing to swap packets with each other. 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<mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org<mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Is there any good reason why you (and all the others) are not waving torches and pitchforks? niftybunny abuse@to-surf-and-protect.net
On 24 Jan 2017, at 05:28, John Ricketts <john@quintex.com> wrote:
I am forced to peer with both Cogent and HE because of this.
On Jan 23, 2017, at 22:28, niftybunny <abuse@to-surf-and-protect.net <mailto:abuse@to-surf-and-protect.net>> wrote:
BGP should choose another path? BGP Routing is highly “political” but IPs just black holed is really really bad … If this is true: WTF?!
niftybunny abuse@to-surf-and-protect.net <mailto:abuse@to-surf-and-protect.net>
On 24 Jan 2017, at 05:24, teor <teor2345@gmail.com <mailto:teor2345@gmail.com>> wrote:
On 24 Jan 2017, at 15:18, niftybunny <abuse@to-surf-and-protect.net <mailto:abuse@to-surf-and-protect.net>> wrote:
Could I get an ELI5 for this please?
If you want an ELI5, explain your request like I'm five years old.
On 24 Jan 2017, at 04:40, John Ricketts <john@quintex.com <mailto:john@quintex.com>> wrote:
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation…
When two big internet companies don't agree on who pays when they swap packets, they punish their users by refusing to swap packets with each other.
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 <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Tue, 24 Jan 2017 03:40:05 +0000 John Ricketts <john@quintex.com> wrote:
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation...
Any basis for that in this case? Other than "a random thing I remember about IPv6, so I'll mention it regardless of whether relevant, to further confuse the discussion". According to http://bgp.he.net/AS54290#_graph6 AS54290 Hostwinds is connected both to Cogent and HE.net, so this shouldn't be the issue here.
On Jan 23, 2017, at 21:38, teor <teor2345@gmail.com> wrote:
On 24 Jan 2017, at 14:31, niftybunny <abuse@to-surf-and-protect.net> wrote:
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.
$ wget dist.torproject.org --2017-01-24 03:34:08-- http://dist.torproject.org/ Resolving dist.torproject.org (dist.torproject.org)... 2001:41b8:202:deb:213:21ff:fe20:1426, 2620:0:6b0:b:1a1a:0:26e5:4810, 2a01:4f8:172:1b46:0:abba:5:1, ... Connecting to dist.torproject.org (dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:80... connected. HTTP request sent, awaiting response... 302 Found ...
dist.torproject.org works over IPv6 via a US Hurricane Electric tunnel, and from OVH in France and Canada, so I'd check with your provider.
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
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- With respect, Roman
Sigh. And this is why I rarely post. I'll take my toys and go home now. For what it's worth, you're right.... if Hostwinds peers with both then I'm wrong. It certainly won't be the first mistake I've made day. :-) John
On Jan 23, 2017, at 23:00, Roman Mamedov <rm@romanrm.net> wrote:
On Tue, 24 Jan 2017 03:40:05 +0000 John Ricketts <john@quintex.com> wrote:
It is entirely possible this is a result of the HE vs Cogent feud, big break in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure where they are in that negotiation...
Any basis for that in this case? Other than "a random thing I remember about IPv6, so I'll mention it regardless of whether relevant, to further confuse the discussion". According to http://bgp.he.net/AS54290#_graph6 AS54290 Hostwinds is connected both to Cogent and HE.net, so this shouldn't be the issue here.
On Jan 23, 2017, at 21:38, teor <teor2345@gmail.com> wrote:
On 24 Jan 2017, at 14:31, niftybunny <abuse@to-surf-and-protect.net> wrote:
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.
$ wget dist.torproject.org --2017-01-24 03:34:08-- http://dist.torproject.org/ Resolving dist.torproject.org (dist.torproject.org)... 2001:41b8:202:deb:213:21ff:fe20:1426, 2620:0:6b0:b:1a1a:0:26e5:4810, 2a01:4f8:172:1b46:0:abba:5:1, ... Connecting to dist.torproject.org (dist.torproject.org)|2001:41b8:202:deb:213:21ff:fe20:1426|:80... connected. HTTP request sent, awaiting response... 302 Found ...
dist.torproject.org works over IPv6 via a US Hurricane Electric tunnel, and from OVH in France and Canada, so I'd check with your provider.
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
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- With respect, Roman
participants (4)
-
John Ricketts -
niftybunny -
Roman Mamedov -
teor