OVH Community, your new community space.

Can't resolve ipv6 anymore

09-10-2010, 09:20
Any news on that?
Was away for my holidays, and did not check my server if IPv6 is working again.
It still is not working, but also see no reason why I should open a ticket if this is a known issue.

13-09-2010, 11:20
Are there any updates on this issue? My tickets been open for over a week now with no progress

07-09-2010, 15:20

We are aware after changing our networking configuration that some clients IPV6 setup is not working at the moment I cannot give a resolution, but Octave/Oles is personally working on it.

07-09-2010, 11:33
fozl: i currently have a ticket open regarding the same issue too (Ticket 533290), started midday thursday, haven't been able to use ipv6 on my RPS since. Seems to be an identical problem as posted in this thread.

07-09-2010, 10:47
Could you try again to make a ticket? Or just email us your details etc and we'll open it for you.

07-09-2010, 10:18
LOL @ Ticket System:

Incident ticket
There are too many characters

Can anyone from OVH please have a look at this thread instead, not in the mood to retry the ticket creation.

05-09-2010, 15:41
One thing which seem odd to me.
If I'm correct looking at the following,

PHP Code:
15:25:43.705982 IP6 fe80::222:91ff:fe08:400 ff02::1ICMP6router advertisementlength 64 
is fe80::222:91ff:fe08:400 sending an router advertisement to ff02::1 (All nodes)

I can ping that ipv6:

PHP Code:
# ping6 -I eth0 fe80::222:91ff:fe08:400
PING fe80::222:91ff:fe08:400(fe80::222:91ff:fe08:400from 2001:41d0:2:21a::9 eth056 data bytes
64 bytes from fe80
::222:91ff:fe08:400icmp_seq=1 ttl=64 time=166 ms
64 bytes from fe80
::222:91ff:fe08:400icmp_seq=2 ttl=64 time=76.0 ms
64 bytes from fe80
::222:91ff:fe08:400icmp_seq=3 ttl=64 time=44.1 ms
64 bytes from fe80
::222:91ff:fe08:400icmp_seq=4 ttl=64 time=116 ms
64 bytes from fe80
::222:91ff:fe08:400icmp_seq=5 ttl=64 time=68.8 ms 
But have no idea where this belongs to, and is not from my ipv6 range. But looking at the RTT, it looks like to be outside of the OVH network?

05-09-2010, 15:23
Quote Originally Posted by raidensnake
i don't get the concept behind ipv6 that much. it's a shame someone doesn't explain how to set one up cause I've only ever dealt with ipv4.
There are guides avail. in the OVH wiki

05-09-2010, 15:22
That was my first thought.
Funny enough I can ping my OVH gateway from Home via the 6to4 Sixxs tunnel, so it is online.
Will do some more testing, and most likely ask OVH to have a look at it on monday.

Thanks again Myatu

05-09-2010, 15:17
i don't get the concept behind ipv6 that much. it's a shame someone doesn't explain how to set one up cause I've only ever dealt with ipv4.

05-09-2010, 15:10
So a solicitation is sent out and not answered anywhere. You ought to see something like:

IP6 2001:41d0:2:2ff:ff:ff:ff:ff > fe80::ff:fe00:73c: ICMP6, neighbor advertisement, tgt is 2001:41d0:2:2ff:ff:ff:ff:ff, length 32
Now, I had something similar before, but that was MAC associated. This appears to be an issue on OVH's side, IMO, so perhaps time for a ticket (make sure you also include "ip -6 route show" in the ticket along with the above tcpdump output showing no answer).

05-09-2010, 14:17
PHP Code:
# ip -6 neigh show
2001:41d0:2:2ff:ff:ff:ff:ff dev eth0  router FAILED 
And thats what I get from tcpdump if I try a ping6

PHP Code:
# tcpdump -n -i eth0 ip6
tcpdumpverbose output suppressed, use -or -vv for full protocol decode
listening on eth0
link-type EN10MB (Ethernet), capture size 65535 bytes
:05:13.388719 IP6 2001:41d0:2:21a::2.5353 ff02::fb.53530 PTR (QM)? (44)
14:05:43.284657 IP6 2001:41d0:2:21a::dead:beef ff02::1:ffff:ffICMP6neighbor solicitationwho has 2001:41d0:2:2ff:ff:ff:ff:fflength 32
14:07:03.766857 IP6 fe80::222:91ff:fe08:400 ff02::1ICMP6router advertisementlength 64
:10:24.268034 IP6 fe80::222:91ff:fe08:400 ff02::1ICMP6router advertisementlength 64 
Thanks for helping me btw

05-09-2010, 13:21
What does "ip -6 neigh show" give? You can also run a tcpdump (ie, "tcpdump -n -i eth0 ip6" to see all IPv6 packets).

05-09-2010, 07:47
Yes, as per ifconfig above, that is one of the ipv6 configured on eth0.

Here is the network/interface bit of it

PHP Code:
        iface eth0 inet6 static
address 2001:41d0:2:21a::dead:beef/56
        netmask 56
        gateway 2001
Here is another ipv6 configured: 2001:41d0:2:21a::2

And here is my traceroute:

PHP Code:
# traceroute6 2001:41D0:2:2FF:FF:FF:FF:FF
traceroute to 2001:41D0:2:2FF:FF:FF:FF:FF (2001:41d0:2:2ff:ff:ff:ff:fffrom 2001:41d0:2:21a::dead:beefport 33434from port 4473730 hops max60 byte packets
 1  derchris
.eu (2001:41d0:2:21a::dead:beef)  3005.173 ms !H  3003.878 ms !H  3003.924 ms !
Got this from the man page:

!H Address unreachable
The host address is not reachable for some other reasons, particularly a link-layer failure (e.g. Neighbor discovery failure).

04-09-2010, 23:29
From another IPv6 network (Hurricane Electric):

# ping6 2001:41d0:2:2ff:ff:ff:ff:ff
PING 2001:41d0:2:2ff:ff:ff:ff:ff(2001:41d0:2:2ff:ff:ff:ff:ff) 56 data bytes
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=1 ttl=54 time=28.6 ms
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=2 ttl=54 time=28.3 ms
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=3 ttl=54 time=27.9 ms
64 bytes from 2001:41d0:2:2ff:ff:ff:ff:ff: icmp_seq=4 ttl=54 time=28.1 ms
So that seems ok. Is "dead:beef" the actual IP? As that seems to be blocking pings, but appears routable:

 # traceroute6 2001:41d0:2:21a::dead:beef
traceroute to 2001:41d0:2:21a::dead:beef (2001:41d0:2:21a::dead:beef), 30 hops max, 80 byte packets
 1 *** (2001:470:***::1)  5.969 ms  9.787 ms  13.316 ms
 2 (2001:470:0:67::1)  18.518 ms  18.635 ms  18.626 ms
 3  2001:7f8:4::1587:1 (2001:7f8:4::1587:1)  13.857 ms  13.934 ms  13.905 ms
 4  2001:688:0:2:7::fe (2001:688:0:2:7::fe)  33.318 ms  33.277 ms  33.231 ms
 5  2001:688:0:2:5::f9 (2001:688:0:2:5::f9)  26.928 ms  26.984 ms  26.814 ms
 6  2001:688:0:3:7::76 (2001:688:0:3:7::76)  27.153 ms  15.593 ms  15.544 ms
 7  2001:41d0::601 (2001:41d0::601)  221.833 ms * *
 8  * * 2001:41d0::803 (2001:41d0::803)  27.359 ms
 9  * * *
10  * * *
11  * * *
12  * * *^C

04-09-2010, 22:41
Hi all,

got ipv6 configured on my boxes ages ago, never touched it since then, was working fine.
Got a download today, which DNS first gave me a ipv6, but it couldn't resolve.
Then I checked my system, and I can't reach the ipv6 gateway.
Checked, but there are no know issues/maintenance for this, at least i couldn't find one.
Config should be ok, as not touched since last time.
Can ping local ipv6 no problem, just cant reach the gateway.

PHP Code:
# ping6 2001:41d0:2:2ff:ff:ff:ff:ff
PING 2001:41d0:2:2ff:ff:ff:ff:ff(2001:41d0:2:2ff:ff:ff:ff:ff56 data bytes
From 2001
:41d0:2:21a::dead:beef icmp_seq=1 Destination unreachableAddress unreachable 
PHP Code:
~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:30:48:d3:aa:74
            inet6 addr
2001:41d0:2:21a::dead:beef/56 Scope:Global 
Not sure what else to check, not played around with ipv6 that much, but would say Gateway down?

Any more thought on that?
Thanks in advance.