All IPv6 network is down/unreachable, is there any maintenance window running or known issues?
IPv6 network is down/unreachable
- nbari
- Erledigt
-
-
What do you mean by "all IPv6 networks"?
-
My monitoring has reported a small packet loss or increased ping times to one IPv6 destination in NYC since yesterday late evening. Everything is back to normal since ~30 minutes. No other destinations have been affected.
Edit: my monitoring checks are done by a Netcup root server. -
What do you mean by "all IPv6 networks"?
At least in all the VM's I have, the IPv6 networks are unreachable, I can't either ping VM's within netcup.
-
At least in all the VM's I have, the IPv6 networks are unreachable, I can't either ping VM's within netcup.
What does traceroute6 show?
-
Code
traceroute6 to google.com (2a00:1450:4001:809::200e) from 2a03:4000:40:218::1, 64 hops max, 20 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * *
In another VM, It just started to work:
Code
Alles anzeigen> traceroute6 google.com traceroute6 to google.com (2a00:1450:4016:804::200e) from 2a03:4000:26:1fd::1, 64 hops max, 20 byte packets 1 2a03:4000:26::3 0.278 ms 7.619 ms 5.429 ms 2 2a00:11c0:47:3::20 2.210 ms 0.782 ms 0.723 ms 3 2a00:11c0:47:1:47::141 3.768 ms 3.718 ms 3.789 ms 4 2001:4860:1:1::6bc 3.989 ms 3.793 ms 3.702 ms 5 2001:4860:0:11e1::f 4.608 ms 2001:4860:0:11e2::2 3.858 ms 3.794 ms 6 2001:4860::8:0:cb95 10.934 ms 11.122 ms 2001:4860::c:4000:f873 5.428 ms 7 2001:4860::c:4001:e5d7 10.999 ms 2001:4860::c:4001:e5e9 14.678 ms 2001:4860::c:4001:5638 10.575 ms 8 2001:4860::9:4000:cf86 10.935 ms 2001:4860::9:4001:5634 11.889 ms 10.899 ms 9 2001:4860:0:1::35c3 10.855 ms 2001:4860:0:12::1 10.733 ms 2001:4860:0:1::35c1 10.706 ms 10 2001:4860:0:1::35c3 10.398 ms 2001:4860:0:1::35c1 11.549 ms 2001:4860:0:1::35c3 10.219 ms 11 muc12s05-in-x0e.1e100.net 10.541 ms 10.942 ms 10.784 ms
-
do you configuered ipv6 correctly?
sysctl.conf ( German Link: https://www.netcup-wiki.de/wik…nd_Ubuntu_.28bis_17.04.29 )
-
Same problem from your side? for now only 1 VM started to work but all others have issues.
-
I am using FreeBSD but has been working perfectly for years, this is indeed the first issue I have (something very good to say to be honest)
-
-
Is IPv6 working in the rescue system (grml)?
-
In the last week we had multiple people reporting IPv6 problems with BSD.
Please report that to the support. Make sure you mention BSD.
-
I confirm is also not working from the linux rescue system (grml)
-
If it’s not working in the rescue system, you should contact support and mention that.
-
I also tried a FreeBSD Setup a few days ago on a VPS and had the same problems.
I cant find any solution for the problem, so i got back to my debian snapshot. But this wont solve your problem..
You should contact the netcup support. Please also make sure to referr to this forum thread in your ticket. And please keep us up to date!
-
probably related: https://forum.netcup.de/netcup…e-routing-q-a/#post138294
I can reach ping/traceroute some hosts like:
ping6 ipv6help.de
ping6 h3tzner.de (The message contains censored ... )
But I can't reach ipv6.google.com, cloudflare.com etc. (randomly works, but most of the time not)
-
I can reach ping/traceroute some hosts like:
ping6 ipv6help.de
ping6 h3tzner.de (The message contains censored ... )
But I can't reach ipv6.google.com, cloudflare.com etc. (randomly works, but most of the time not)
I have similar issue, ipv6help.de is reachable but ipv6.google.com isn't
From my point of view some kind of a routing issue.
-
In my case randomly works, but is affecting all my services since also adds multiple timeouts to the responses.
Hope this could be fixed soon.
-
In my case randomly works, but is affecting all my services since also adds multiple timeouts to the responses.
Hope this could be fixed soon.
Have you reported this issue to the support?
-
Sorry for my mistake. I do have the same problem with a newly installed vserver.
My solution was to ping netcup.de via ping6 until the ipv6 connectivity worked. After a reboot the connectivity is gone again which means you need to ping any ipv6-host again. This usually takes between 5 and 15 minutes until the first ping gets answered..
Edit: My original message in german:
Habe ein ähnliches Phänomen festgestellt. Habe ein paar vserver bzw. root-server auf verschiedenen Accounts. Bisher hat IPv6 nach Neubestellung und Neuinstallation von minimal-Systemen problemlos funktioniert.
Vergangene Woche habe ich einen weiteren vserver bestellt und IPv6 hat erstmal nicht funktioniert. Nach ein bisschen hin- und herprobieren (hauptsächlich einfach einen ping6 auf netcup.de laufen lassen) war die IPv6-Konnektivität auf einmal da und nach einem Reboot wieder weg.
Ich habe dann das System ins Rescue gebootet - IPv6 ging auch hier nicht. Dann widerrum erneut Ubuntu 18 minimal installiert und wieder die gleichen Probleme.
Support habe ich bisher noch nicht kontaktiert, da ich momentan wenig Zeit habe mich da lange drum zu kümmern (man wird wahrscheinlich erstmal davon ausgehen, dass der Kunde den Fehler macht, was ja auch häufig der Fall ist. Die Tage hatte ich aber zu viel um die Ohren um alles nochmal sauber zu dokumentieren und den Support zu kontaktieren).
Lange Rede, kurzer Sinn:
Wenn IPv6 auf der Maschine nicht geht, in der Shell einen ping6 auf netcup.de absetzen und warten. Bei meinen Tests hat es i.d.R. zwischen 5 und 15 Minuten gedauert, bis der erste Ping beantwortet wurde und damit IPv6 funktioniert. Falls jemand Zeit und Lust hat, kann er den Support auch gerne auf diesen Thread verweisen. Ab dem Wochenende sollte ich ggf. mal ein bisschen mehr Zeit haben, um die Erkenntnisse nochmal sauber zu dokumentieren.