OVH Community, your new community space.

IPv6 Problem


Patrick.Othmer
09/09/2015, 20h09
Support finally solved problem. Problem exists since 27/05/2015 and ticket also created at same day.

Problem was a ? miss configured ? HSRP rule. Thanks to Jan and the technicians of OVH

janus57
30/08/2015, 14h31
Hello,

contact the support maybe ?

Cordially, janus57

Patrick.Othmer
30/08/2015, 11h19
Problem still exists:
IPv6:
root@patrick-othmer:~# ping6 ubuntu.mirrors.ovh.net
PING ubuntu.mirrors.ovh.net(2001:41d0:1:7c8b::1) 56 data bytes
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=14 ttl=62 time=0.682 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=15 ttl=62 time=0.753 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=16 ttl=62 time=1.46 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=17 ttl=62 time=0.638 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=18 ttl=62 time=0.788 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=19 ttl=62 time=1.90 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=20 ttl=62 time=0.606 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=21 ttl=62 time=0.737 ms
64 bytes from 2001:41d0:1:7c8b::1: icmp_seq=22 ttl=62 time=0.620 ms
^C
--- ubuntu.mirrors.ovh.net ping statistics ---
22 packets transmitted, 9 received, 59% packet loss, time 21114ms
rtt min/avg/max/mdev = 0.606/0.910/1.908/0.433 ms

IPv4:
root@patrick-othmer:~# ping ubuntu.mirrors.ovh.net
PING mir4.ovh.net (91.121.125.139) 56(84) bytes of data.
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=1 ttl=62 time=0.463 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=2 ttl=62 time=0.628 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=3 ttl=62 time=0.585 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=4 ttl=62 time=0.622 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=5 ttl=62 time=0.545 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=6 ttl=62 time=0.505 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=7 ttl=62 time=0.517 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=8 ttl=62 time=0.536 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=9 ttl=62 time=0.448 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=10 ttl=62 time=0.562 ms
64 bytes from mir2.ovh.net (91.121.125.139): icmp_seq=11 ttl=62 time=0.539 ms
^C
--- mir4.ovh.net ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 13637ms
rtt min/avg/max/mdev = 0.448/0.540/0.628/0.063 ms

Patrick.Othmer
13/07/2015, 23h38
Problem still exist:
Home -> Host
Start: Mon Jul 13 22:30:59 2015
HOST: * Loss% Snt Last Avg Best Wrst StDev
1.|-- 2001:a61:*:*:*:* 0.0% 10 0.6 0.6 0.6 0.7 0.0
2.|-- 2001:a60::89:103:1 0.0% 10 48.5 47.8 47.2 48.5 0.0
3.|-- 2001:a60::69:0:2:2 0.0% 10 39.7 40.3 39.7 41.0 0.0
4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5.|-- 2001:41d0::27f 20.0% 10 48.3 49.1 47.9 50.3 0.5
6.|-- vss-8b-6k.fr.eu 0.0% 10 52.2 102.3 48.6 245.1 68.7
7.|-- uptime-solutions.de 0.0% 10 48.9 48.7 47.4 49.5 0.3

Host -> Home
Start: Mon Jul 13 22:38:42 2015
HOST: patrick-othmer.de Loss% Snt Last Avg Best Wrst StDev
1.|-- vss-8b-6k.fr.eu 0.0% 10 74.4 8.2 0.8 74.4 23.3
2.|-- rbx-g1-a9.fr.eu 0.0% 10 1.3 2.2 1.3 4.4 0.7
3.|-- 2001:41d0::27e 40.0% 10 8.6 8.7 8.5 9.0 0.0
4.|-- rt-decix-2.m-online.net 0.0% 10 8.7 8.6 8.5 8.7 0.0
5.|-- 2001:a60::89:103:1 0.0% 10 28.7 28.0 27.8 28.7 0.0
6.|-- 2001:a61:*:*:*:* 10.0% 10 47.8 48.1 47.6 48.5 0.0

Home -> google.de
Start: Mon Jul 13 22:43:52 2015
HOST: * Loss% Snt Last Avg Best Wrst StDev
1.|-- 2001:a61:*:*:*:* 0.0% 10 0.7 0.6 0.6 1.0 0.0
2.|-- 2001:a60::89:103:1 0.0% 10 47.8 73.3 47.0 185.3 43.8
3.|-- rt-inxs.m-online.net 0.0% 10 34.1 46.3 33.3 80.1 19.1
4.|-- 2001:a60:0:106::2 0.0% 10 33.4 46.2 33.2 80.3 19.6
5.|-- 2001:4860::1:0:336d 0.0% 10 33.3 48.1 33.3 83.6 20.3
6.|-- 2001:4860::8:0:8bd7 0.0% 10 37.1 47.7 33.4 82.7 20.6
7.|-- 2001:4860::8:0:5039 0.0% 10 40.0 48.4 39.9 83.2 16.5
8.|-- 2001:4860::8:0:5e19 0.0% 10 49.9 70.9 48.7 131.1 34.8
9.|-- 2001:4860::8:0:4398 0.0% 10 120.2 138.7 119.9 191.0 29.1
10.|-- 2001:4860::8:0:9150 0.0% 10 147.3 161.8 146.3 214.9 26.6
11.|-- 2001:4860::8:0:7894 0.0% 10 146.5 154.4 146.3 192.0 14.9
12.|-- 2001:4860::2:0:733f 0.0% 10 146.7 152.8 146.1 175.4 11.1
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- iv-in-x5e.1e100.net 10.0% 10 146.7 156.8 146.2 187.0 16.2

Patrick.Othmer
02/07/2015, 08h18
Problem still exists:
Do 2. Jul 07:18:08 CEST 2015
PING patrick-othmer.de(uptime-solutions.de) 56 data bytes
64 bytes from uptime-solutions.de: icmp_seq=10 ttl=58 time=50.0 ms
64 bytes from uptime-solutions.de: icmp_seq=11 ttl=58 time=51.0 ms
64 bytes from uptime-solutions.de: icmp_seq=12 ttl=58 time=49.8 ms
64 bytes from uptime-solutions.de: icmp_seq=13 ttl=58 time=50.4 ms
64 bytes from uptime-solutions.de: icmp_seq=14 ttl=58 time=49.7 ms
64 bytes from uptime-solutions.de: icmp_seq=15 ttl=58 time=49.4 ms
64 bytes from uptime-solutions.de: icmp_seq=16 ttl=58 time=50.5 ms
64 bytes from uptime-solutions.de: icmp_seq=17 ttl=58 time=51.5 ms
64 bytes from uptime-solutions.de: icmp_seq=18 ttl=58 time=49.4 ms
^C
--- patrick-othmer.de ping statistics ---
18 packets transmitted, 9 received, 50% packet loss, time 17084ms
rtt min/avg/max/mdev = 49.418/50.223/51.508/0.696 ms

Patrick.Othmer
22/06/2015, 19h51
Date: Mo 22. Jun 18:45:03 CEST 2015
ping6 2001:41d0:8:783f::1
PING 2001:41d0:8:783f::1(2001:41d0:8:783f::1) 56 data bytes
^C
--- 2001:41d0:8:783f::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

Date: Mo 22. Jun 18:50:38 CEST 2015
ping6 2001:41d0:8:783f::1
PING 2001:41d0:8:783f::1(2001:41d0:8:783f::1) 56 data bytes
64 bytes from 2001:41d0:8:783f::1: icmp_seq=1 ttl=58 time=46.9 ms
64 bytes from 2001:41d0:8:783f::1: icmp_seq=2 ttl=58 time=46.3 ms
64 bytes from 2001:41d0:8:783f::1: icmp_seq=3 ttl=58 time=46.4 ms
64 bytes from 2001:41d0:8:783f::1: icmp_seq=4 ttl=58 time=46.9 ms
^C
--- 2001:41d0:8:783f::1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 46.321/46.656/46.936/0.383 ms

Edit:
Date: Mo 22. Jun 18:56:00 CEST 2015
PING patrick-othmer.de(uptime-solutions.de) 56 data bytes
64 bytes from uptime-solutions.de: icmp_seq=17 ttl=58 time=46.2 ms
64 bytes from uptime-solutions.de: icmp_seq=18 ttl=58 time=46.8 ms
64 bytes from uptime-solutions.de: icmp_seq=19 ttl=58 time=52.3 ms
64 bytes from uptime-solutions.de: icmp_seq=20 ttl=58 time=46.9 ms
64 bytes from uptime-solutions.de: icmp_seq=21 ttl=58 time=46.7 ms
64 bytes from uptime-solutions.de: icmp_seq=22 ttl=58 time=45.9 ms
^C
--- patrick-othmer.de ping statistics ---
23 packets transmitted, 6 received, 73% packet loss, time 22135ms
rtt min/avg/max/mdev = 45.947/47.515/52.317/2.183 ms

Patrick.Othmer
22/06/2015, 19h49
Open again. Problem still exists and now with ipv4:
PING patrick-othmer.de (37.59.61.63) 56(84) bytes of data.
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=1 ttl=57 time=118 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=2 ttl=57 time=120 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=3 ttl=57 time=117 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=4 ttl=57 time=95.0 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=5 ttl=57 time=107 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=6 ttl=57 time=118 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=7 ttl=57 time=111 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=8 ttl=57 time=105 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=9 ttl=57 time=119 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=10 ttl=57 time=112 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=11 ttl=57 time=108 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=12 ttl=57 time=107 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=14 ttl=57 time=130 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=15 ttl=57 time=111 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=16 ttl=57 time=112 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=17 ttl=57 time=120 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=18 ttl=57 time=109 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=19 ttl=57 time=104 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=20 ttl=57 time=119 ms
64 bytes from uptime-solutions.de (37.59.61.63): icmp_seq=21 ttl=57 time=99.4 ms
^C
--- patrick-othmer.de ping statistics ---
21 packets transmitted, 20 received, 4% packet loss, time 20034ms
rtt min/avg/max/mdev = 95.083/112.370/130.830/8.117 ms

Date: So 21. Jun 17:04:29 CEST 2015

Patrick.Othmer
21/06/2015, 11h04
I got a answer after 2 Weeks. Problem is solved now.

samip537
10/06/2015, 01h34
Not exactly the same problem, but IPv6 is broken on my server too....

Patrick.Othmer
05/06/2015, 08h46
route -A inet6
Destination Next Hop Flag Met Ref Use If
2001:41d0:8:783f::1/128 :: U 256 0 0 eth0
2001:41d0:8:78ff:ff:ff:ff:ff/128 :: U 1024 0 4 eth0
2001:41d0:8:7800::/56 :: UAe 256 0 0 eth0
fe80::/64 :: U 256 0 0 eth0
::/0 2001:41d0:8:78ff:ff:ff:ff:ff UG 1024 0 0 eth0
::/0 :: !n -1 1 33711 lo
::1/128 :: Un 0 1 3157 lo
2001:41d0:8:783f::1/128 :: Un 0 1413128 lo
fe80::222:4dff:fe7a:54aa/128 :: Un 0 1 533 lo
ff00::/8 :: U 256 0 0 eth0
::/0 :: !n -1 1 33711 lo


ip -6 route show
2001:41d0:8:783f::1 dev eth0 proto kernel metric 256
2001:41d0:8:78ff:ff:ff:ff:ff dev eth0 metric 1024
2001:41d0:8:7800::/56 dev eth0 proto kernel metric 256 expires 1727487sec
fe80::/64 dev eth0 proto kernel metric 256
default via 2001:41d0:8:78ff:ff:ff:ff:ff dev eth0 metric 1024

Patrick.Othmer
05/06/2015, 08h31
Before 7 days I have the support request sent but received no reply so far. Kimsufi has already violated the network SLA 99.9%.
I'll look for another provider.

Patrick.Othmer
01/06/2015, 19h53
Still no reply from support. Just to say it's a clean server installation without kernel modification or sysctl "tuning".

Patrick.Othmer
28/05/2015, 20h14
Thank you for your help in advance.

Normal traceroute, if IPv6 connection is available:
traceroute to mir4.ovh.net (2001:41d0:1:7c8b::1) from 2001:41d0:8:783f::1, 30 hops max, 24 byte packets
1 vss-8b-6k.fr.eu (2001:41d0:8:78ff:ff:ff:ff:fd) 6.429 ms 4.22 ms 3.623 ms
2 rbx-s15-6k.fr.eu (2001:41d0::200f) 1.274 ms 1.378 ms 1.364 ms
3 2001:41d0:1:7c8b::1 (2001:41d0:1:7c8b::1) 0.619 ms 0.81 ms 0.661 ms

traceroute at downtime:
traceroute to mir4.ovh.net (2001:41d0:1:7c8b::1) from 2001:41d0:8:783f::1, 30 hops max, 24 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * 2001:41d0:1:7c8b::1 (2001:41d0:1:7c8b::1) 0.839 ms

Ping with downtime from a other server:
PING patrick-othmer.de(uptime-solutions.de) 56 data bytes
64 bytes from uptime-solutions.de: icmp_seq=17 ttl=56 time=20.9 ms
64 bytes from uptime-solutions.de: icmp_seq=18 ttl=56 time=21.0 ms
64 bytes from uptime-solutions.de: icmp_seq=19 ttl=56 time=20.9 ms
64 bytes from uptime-solutions.de: icmp_seq=20 ttl=56 time=21.0 ms
64 bytes from uptime-solutions.de: icmp_seq=21 ttl=56 time=20.9 ms
64 bytes from uptime-solutions.de: icmp_seq=22 ttl=56 time=21.0 ms
64 bytes from uptime-solutions.de: icmp_seq=23 ttl=56 time=21.0 ms
64 bytes from uptime-solutions.de: icmp_seq=24 ttl=56 time=20.9 ms
64 bytes from uptime-solutions.de: icmp_seq=25 ttl=56 time=20.9 ms
64 bytes from uptime-solutions.de: icmp_seq=26 ttl=56 time=20.9 ms
64 bytes from uptime-solutions.de: icmp_seq=27 ttl=56 time=21.1 ms
64 bytes from uptime-solutions.de: icmp_seq=28 ttl=56 time=21.1 ms
64 bytes from uptime-solutions.de: icmp_seq=29 ttl=56 time=20.9 ms
^C
--- patrick-othmer.de ping statistics ---
29 packets transmitted, 13 received, 55% packet loss, time 28148ms
rtt min/avg/max/mdev = 20.913/21.006/21.135/0.198 ms

Traceroute with available connection from other server:
traceroute to patrick-othmer.de (2001:41d0:8:783f::1) from 2a02:1b***, 30 hops max, 24 byte packets
1 2a02:1b**** (2a02:1b****) 0.281 ms 0.177 ms 0.144 ms
2 2a02:1b**** (2a02:1b****) 1.131 ms 0.587 ms 0.77 ms
3 2a02:1b**** (2a02:1b****) 0.554 ms 0.441 ms 0.361 ms
4 2a02:1b**** (2a02:1b****) 1.425 ms 1.053 ms 0.622 ms
5 2001:7f8:30:0:2:1:1:6276 (2001:7f8:30:0:2:1:1:6276) 150.867 ms 25.929 ms 1.49 ms
6 mil-1-6k.it.eu (2001:41d0::651) 13.328 ms 13.69 ms 13.194 ms
7 rbx-g1-a9.fr.eu (2001:41d0::b41) 20.987 ms 20.948 ms 20.954 ms
8 vss-8b-6k.fr.eu (2001:41d0::171) 20.913 ms 20.736 ms 20.742 ms
9 uptime-solutions.de (2001:41d0:8:783f::1) 21.015 ms 20.879 ms 20.84 ms

Looks like vss-8b-6k.fr.eu have routing problems?

nowwhat
28/05/2015, 01h08
A traceroute6 is possible ?

'ping' is and stays a very low priority protocol, do you have other 'ipv6-tcp' problems ?

Patrick.Othmer
27/05/2015, 20h30
I have sporadic connection problems with IPv6. Escaping the sysctl parameters did not help.

Test:
ping6 ubuntu.mirrors.ovh.net
PING ubuntu.mirrors.ovh.net(mir4.ovh.net) 56 data bytes
^C
--- ubuntu.mirrors.ovh.net ping statistics ---
30 packets transmitted, 0 received, 100% packet loss, time 29231ms

Disabling of IPv6 is not a solution. I have not received a response from support so far.
Anyone can help? Thank you in advance.

PS: Sry for my bad english. I'am from germany.