FYI: Rsync is currently failing for me via IPv6 to mirror located at: 2001:49f0:d071:1::4. Other IPv6 locations are working just fine.
Adam
On Tue, Apr 4, 2017 at 4:01 PM, Anssi Johansson avij@centosproject.org wrote:
How is it failing? It seems to work OK from here at least now.
It is simply timing while trying to sync from my mirror. Running this test, produces:
rsync -azqH [2001:49f0:d071:1::4]::CentOS/timestamp.txt /tmp/ rsync: failed to connect to 2001:49f0:d071:1::4 (2001:49f0:d071:1::4): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
I just tried it now, and it is still failing. My v6 address is: 2001:18b0:ffff:31f1::9 and I am able to sync from other IPv6 hosts it just seems like, for me at least, this host is not reachable. It also doesn't respond to ping attempts from my host.
Thanks, Adam
On 05/04/17 14:41, Adam Ring wrote:
On Tue, Apr 4, 2017 at 4:01 PM, Anssi Johansson <avij@centosproject.org mailto:avij@centosproject.org> wrote:
How is it failing? It seems to work OK from here at least now.It is simply timing while trying to sync from my mirror. Running this test, produces:
rsync -azqH [2001:49f0:d071:1::4]::CentOS/timestamp.txt /tmp/ rsync: failed to connect to 2001:49f0:d071:1::4 (2001:49f0:d071:1::4): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
I just tried it now, and it is still failing. My v6 address is: 2001:18b0:ffff:31f1::9 and I am able to sync from other IPv6 hosts it just seems like, for me at least, this host is not reachable. It also doesn't respond to ping attempts from my host.
Thanks, Adam
So if it's a routing issue, maybe the best option would be to open a ticket with your ISP to troubleshoot this and see where it stops ? (including traceroute/mtr reports, etc)
5.4.2017, 15.41, Adam Ring kirjoitti:
On Tue, Apr 4, 2017 at 4:01 PM, Anssi Johansson <avij@centosproject.org mailto:avij@centosproject.org> wrote:
How is it failing? It seems to work OK from here at least now.It is simply timing while trying to sync from my mirror. Running this test, produces:
rsync -azqH [2001:49f0:d071:1::4]::CentOS/timestamp.txt /tmp/ rsync: failed to connect to 2001:49f0:d071:1::4 (2001:49f0:d071:1::4): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
I just tried it now, and it is still failing. My v6 address is: 2001:18b0:ffff:31f1::9 and I am able to sync from other IPv6 hosts it just seems like, for me at least, this host is not reachable. It also doesn't respond to ping attempts from my host.
As Fabian said, this is likely a routing issue. I can ping6 both your IPv6 address and that msync IPv6 address fine from nine different networks from around the world. Asking from whoever provides your internet connectivity would be the best way forward in this situation. For comparison, here's a working traceroute and ping from one of my servers:
$ traceroute6 2001:49f0:d071:1::4 -A -q1 traceroute to 2001:49f0:d071:1::4 (2001:49f0:d071:1::4), 30 hops max, 80 byte packets 1 2600:3c01::8678:acff:fe0d:79c1 (2600:3c01::8678:acff:fe0d:79c1) [AS63949] 0.781 ms 2 * 3 2600:3c01:3333:5::1 (2600:3c01:3333:5::1) [AS63949] 0.856 ms 4 be2095.ccr22.sjc01.atlas.cogentco.com (2001:550:0:1000::9a36:389) [AS174] 2.431 ms 5 be3178.ccr21.sfo01.atlas.cogentco.com (2001:550:0:1000::9a36:2b45) [AS174] 3.331 ms 6 be3110.ccr21.slc01.atlas.cogentco.com (2001:550:0:1000::9a36:2c8e) [AS174] 18.797 ms 7 be3038.ccr22.den01.atlas.cogentco.com (2001:550:0:1000::9a36:2a62) [AS174] 28.775 ms 8 * 9 2001:550:2:2a::6a:2 (2001:550:2:2a::6a:2) [AS174] 29.741 ms 10 2001:49f0:d071:1::4 (2001:49f0:d071:1::4) [AS30058] 29.297 ms !X
$ ping6 -c3 2001:49f0:d071:1::4 PING 2001:49f0:d071:1::4(2001:49f0:d071:1::4) 56 data bytes 64 bytes from 2001:49f0:d071:1::4: icmp_seq=1 ttl=55 time=29.2 ms 64 bytes from 2001:49f0:d071:1::4: icmp_seq=2 ttl=55 time=29.3 ms 64 bytes from 2001:49f0:d071:1::4: icmp_seq=3 ttl=55 time=29.3 ms
--- 2001:49f0:d071:1::4 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2032ms rtt min/avg/max/mdev = 29.271/29.294/29.310/0.140 ms
As Fabian said, this is likely a routing issue. I can ping6 both your IPv6 address and that msync IPv6 address fine from nine different networks from around the world. Asking from whoever provides your internet connectivity would be the best way forward in this situation. For comparison, here's a working traceroute and ping from one of my servers:
Thank you all for the information, it would appear to be a routing issue outside our network with one of our upstream providers. Thanks for the additional troubleshooting on your end.
Adam
-
Adam Ring -
Anssi Johansson -
Fabian Arrotin