Jump to content
Калькуляторы

У кого сейчас проблемы с ipv6 от netassist

Собственно, с netassist опять проблемы.

 

Вот ping до яндекса:

 

 

ne-vlezay80@vm784816:~$ ping6 ya.ru
PING ya.ru(ya.ru (2a02:6b8::2:242)) 56 data bytes
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=1 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=3 ttl=50 time=114 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=4 ttl=50 time=115 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=5 ttl=50 time=110 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=6 ttl=50 time=110 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=7 ttl=50 time=121 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=8 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=9 ttl=50 time=98.6 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=10 ttl=50 time=94.9 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=11 ttl=50 time=96.6 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=12 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=13 ttl=50 time=115 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=15 ttl=50 time=101 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=16 ttl=50 time=117 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=17 ttl=50 time=114 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=18 ttl=50 time=117 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=19 ttl=50 time=101 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=21 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=22 ttl=50 time=105 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=23 ttl=50 time=117 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=24 ttl=50 time=118 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=25 ttl=50 time=115 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=27 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=28 ttl=50 time=110 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=29 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=31 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=34 ttl=50 time=114 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=35 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=37 ttl=50 time=113 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=38 ttl=50 time=114 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=39 ttl=50 time=121 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=41 ttl=50 time=118 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=42 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=43 ttl=50 time=121 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=44 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=45 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=46 ttl=50 time=115 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=47 ttl=50 time=106 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=48 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=49 ttl=50 time=110 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=50 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=51 ttl=50 time=125 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=52 ttl=50 time=95.6 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=53 ttl=50 time=107 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=54 ttl=50 time=113 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=55 ttl=50 time=116 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=57 ttl=50 time=122 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=58 ttl=50 time=119 ms
64 bytes from ya.ru (2a02:6b8::2:242): icmp_seq=59 ttl=50 time=117 ms
^C
--- ya.ru ping statistics ---
59 packets transmitted, 49 received, 16.9492% packet loss, time 276ms
rtt min/avg/max/mdev = 94.892/113.524/125.041/7.079 ms
ne-vlezay80@vm784816:~$ wget https://mirror.yandex.ru/debian-cd/10.3.0-live/amd64/iso-hybrid/debian-live-10.3.0-amd64-gnome.iso -O- >/dev/null
--2020-04-26 12:01:26--  https://mirror.yandex.ru/debian-cd/10.3.0-live/amd64/iso-hybrid/debian-live-10.3.0-amd64-gnome.iso
Resolving mirror.yandex.ru (mirror.yandex.ru)... 2a02:6b8::183, 213.180.204.183
Connecting to mirror.yandex.ru (mirror.yandex.ru)|2a02:6b8::183|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2537684992 (2.4G) [application/octet-stream]
Saving to: ‘STDOUT’

-                                                                                 0%[                                                                                                                                                                                                      ]   1.33M  19.6KB/s    eta 20h 40m^C

 

Интересно, как у Вас работает ipv6 от туннельного брокера netassist?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.