no IPv6 connectivity from/to vps on japan node (Mininode 5)

mva · 2018-02-03 18:52:27

Hi there!
I'm still (after about a half of year) experience issues with (absence of) IPv6 connectivity on my japan VPS...
Assigned IPv4 is: 172.16.0.247
Assigned IPv6 subnet: 2001:19f0:7000:99e0:2d4::/80
An Ipv6 IP created through SolusVM: 2001:19f0:7000:99e0:2d4:dead:beef:cafe

Traceroute (outgoing):

[email protected]:/#  mtr -wrnc1 2600::
Start: Sat Feb  3 13:51:00 2018
HOST: jp                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2001:19f0:7000:8005:5054:ff:fe1c:28ae  0.0%     1    0.5   0.5   0.5   0.5   0.0
  2.|-- ???                                   100.0     1    0.0   0.0   0.0   0.0   0.0
[email protected]:/#

Incoming:

$ mtr -nwrc1 2001:19f0:7000:99e0:2d4:dead:beef:cafe
Start: 2018-02-04T01:52:18+0700
HOST: note                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 2a03:c700:0:801::1   0.0%     1    2.2   2.2   2.2   2.2   0.0
  2.|-- 2a03:c700:0:101::1   0.0%     1    5.2   5.2   5.2   5.2   0.0
  3.|-- 2a03:c700::1:2:0     0.0%     1    3.4   3.4   3.4   3.4   0.0
  4.|-- 2a03:c700::1:0:2     0.0%     1    2.6   2.6   2.6   2.6   0.0
  5.|-- 2a03:c700::1:1:1     0.0%     1    4.3   4.3   4.3   4.3   0.0
  6.|-- 2a03:c700::1:2:7     0.0%     1    4.8   4.8   4.8   4.8   0.0
  7.|-- 2a00:1e48:1:1::1:46  0.0%     1    8.8   8.8   8.8   8.8   0.0
  8.|-- ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
  9.|-- 2001:de8:5::2:473:1  0.0%     1  219.3 219.3 219.3 219.3   0.0
 10.|-- ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
$

cochon · 2018-02-03 22:00:55

I think this is an ongoing example of the following IPv6 Japan: 100% packet loss after first hop

The Japan IPv6 infrastructure seemed to get switched (in 2016?), and then switched back, leaving several VPSes (including mine) configured in the admin with non functional /80 ranges under 2001:19f0:7000:99e0::

I think you'll have to wait to get the correct subnet assigned to your VPS. I happen to know my old pre-switch working /112 under 2001:19f0:7000:8005 which I now have to configure manually as it's no longer in the admin, but that works for me so I'm not complaining.

mva · 2018-02-04 06:09:43

I've a note about ":8005:" IP-address in clients.inception* panel (although there is nothing about it in vpsadmin.*).
But, unfortunately, when I specify it on the interface, it stopping to work completely (there is not even first hop in the traceroute after that :-/)

Backtogeek · 2018-02-06 13:05:38

When the IP's in japan were switched, it was written about all over here and instructions on claiming your new (working) subnet was sent out.

That was so long ago now I honestly cant remember, I have switched your subnet.

mdoerges · 2018-02-08 15:24:48

Hi, I have the same problem. In the control panel there is still a IPv6 network range with 2001:19f0:7000:99e0 shown. In the client area I see 2001:19f0:7000:8005 IP addresses. But when I manually try to add one of these IP adrdresses I still can't use IPv6.
Control panel user: minivps2351
JP node: IPv4 IP: 172.16.0.128
Can you please also fix my VPS and also add the correct network to the control panel?

bicz · 2018-02-10 10:47:02

i missed that post too, my vps worked (in v6) until 2-3 days ago. tryed to find instructions on forum, didnt find it. any help?

Last edited by bicz (2018-02-10 10:50:12)

vasilevich · 2018-02-11 08:38:17

I add to that, my IPV6 stopped working all of a sudden 2-3 days ago with the exact same problem.
(user : minivps8907 )
these are the IPS I configured in the control panel:
2001:19f0:7000:8005::17b:2/112
2001:19f0:7000:8005::17b:78e6/112

and both are no longer reachable from outside
and the vps is unable to reach any other ip6 network as far as I can tell( I tested against another lowendspirit host which did support ipv6)

please help

thanks!

Backtogeek · 2018-02-11 09:16:15

fixed.

vasilevich · 2018-02-11 09:23:06

it works!

thanks!

mdoerges · 2018-02-12 13:23:30

On my JP VPS IPv6 is still not working. Can this please be checked?
Control panel user: minivps2351
JP node IPv4 IP: 172.16.0.128
In the control panel there's the network 2001:19f0:7000:99e0:34c::/80 shown.
In the client area I see the followong IPs:
2001:19f0:7000:8005:1234:1234:fd71:48a5
2001:19f0:7000:8005:1234:1234:6cf9:9656
2001:19f0:7000:8005:1234:1234:3138:4383
2001:19f0:7000:8005:1234:1234:8a24:7a4
2001:19f0:7000:8005:1234:1234:52e3:2af5
And the VPS had the IP 2001:19f0:7000:8005::f5:1 before it stopped working last week.
Even when I manually try to set up any of these IPs it's still not working. Not pingable.
Can this please be fixed? And can please also the correct network be added to the control panel?

Backtogeek · 2018-02-12 19:52:42

New subnet added, go generate yourself some addresses it should be fine now.

garage151 · 2018-02-13 14:42:23

Hi everyone, I have the same problem too. The new IPv6 not work. Although I have added only 2 IPv6 but in the Control Panel I have Operating System Debian 7 32 bit; IPv6 Address 17. It is possible to fix it. Thanks

garage151 · 2018-02-13 16:37:58

Sorry my Main IP is: 172.16.0.213 Thanks

Phill · 2018-02-23 18:00:04

hello anthony :-)

my last post is long time ago :-D
i have also an ipv6 problem with my tokyo ct. i didn't post earlier because 80% of connectivity problems solved after 1-3 days by it self.
please have a look at my ct 172.16.0.149, there is something wrong with the ipv6 routing. i try to assign different new ipv6 addresses and try to reconfigure network via solusvm. i try to add the gateway inside the ct by my self. but nothing brings me over the second hop.

i think the routing would go over the old (now non existing) gateway.

Host Loss% Snt Last Avg Best Wrst StDev
1. 2001:19f0:7000:8005:5054:ff:fe1c:28ae 0.0% 16 0.5 0.5 0.4 0.6 0.0
2. ???

big thanks!!!

best regards from vienna,
philipp ;-)

ps: sorry for my terrible english :-D

Last edited by Phill (2018-02-23 18:02:31)

Backtogeek · 2018-02-25 15:56:33

garage151 wrote:

Sorry my Main IP is: 172.16.0.213 Thanks

Fixed,

Backtogeek · 2018-02-25 15:58:16

Phill wrote:

hello anthony :-)

big thanks!!!

best regards from vienna,
philipp ;-)

ps: sorry for my terrible english :-D

fixed

Phill · 2018-02-25 16:17:05

Backtogeek wrote:

fixed

big thx :-D

everything is working perfect now.

garage151 · 2018-03-23 18:40:50

Thanks

LowEndSpirit Forum

#1 2018-02-03 18:52:27

no IPv6 connectivity from/to vps on japan node (Mininode 5)

#2 2018-02-03 22:00:55

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#3 2018-02-04 06:09:43

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#4 2018-02-06 13:05:38

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#5 2018-02-08 15:24:48

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#6 2018-02-10 10:47:02

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#7 2018-02-11 08:38:17

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#8 2018-02-11 09:16:15

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#9 2018-02-11 09:23:06

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#10 2018-02-12 13:23:30

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#11 2018-02-12 19:52:42

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#12 2018-02-13 14:42:23

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#13 2018-02-13 16:37:58

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#14 2018-02-23 18:00:04

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#15 2018-02-25 15:56:33

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#16 2018-02-25 15:58:16

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#17 2018-02-25 16:17:05

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

#18 2018-03-23 18:40:50

Re: no IPv6 connectivity from/to vps on japan node (Mininode 5)

Board footer