This happens also in rescue system,so is not a change in my os. But fell free for what you need
IPv6 Root Server
-
DJPRMF -
25. September 2025 um 10:48 -
Erledigt
-
Is the rescue system in general capable of using IPv6?
I have mentioned several times, what I want to see.
-
Is the rescue system in general capable of using IPv6?
You asked for a clean configuration, there is nothing more clean that the rescue system - where it should be the IPv6 configured from scratch, or at least is what makes sense...since is the system used to debug issues, and if Netcup is providing a /64 address, it should be configured there (of course i can't confirm).
I have mentioned several times, what I want to see.
... where?
What you asked i provided, and you said that "is not valid" and is wrong...
-
The rescue system doesn't have IPv6 configured by default, at least it doesn't on my server. You should however be able to boot, press enter at the prompt to get a shell, and then ping fe80::1 (or ping fe80::1%eth0 if there is more than one network interface with an IPv6 link-local address) and get responses. If that doesn't work, it's time to contact customer support.
-
The rescue system doesn't have IPv6 configured by default, at least it doesn't on my server. You should however be able to boot, press enter at the prompt to get a shell, and then ping fe80::1 (or ping fe80::1%eth0 if there is more than one network interface with an IPv6 link-local address) and get responses. If that doesn't work, it's time to contact customer support.
Can only agree to this. I'm pretty sure you have a non-functioning IPv6-Network assigned to your server. So far, your config doesn't look wrong.
