3 ms·

I installed a new bare metal server from a european cloud provider this week. Both my clean Debian and the rescue system couldn’t reach internet through IPv6 d

I installed a new bare metal server from a european cloud provider this week. Both my clean Debian and the rescue system couldn’t reach internet through IPv6 despite getting an address through DHCP. I immediately permanently disabled IPV6. I usually do that pretty late in my installation scripts anyway. I understand the perfect solution didn’t exist and still doesn’t exist, but it’s frustrating. I wish IPv6 could work reliably, not only on major CDNs, and that is appreciated. Then IPv4 would be a vanishing memory.

MaKey 6mo ago
You could have spent a bit of time on debugging the issue. This would have been a great learning opportunity.
- Hackbraten 6mo ago
  It's supposed to Just Work on clean and rescue systems. Otherwise, it's a regression with respect to v4. The fact that it doesn't work is evidence that someone has been doing something wrong. The user at the receiving end of this clusterfuck is not that someone.
- speedgoose 6mo ago
  I agree, but debugging IPv6 issues is pretty far down on the list of things I want to learn.
  - MaKey 6mo ago
    Which european cloud provider is it?
    - speedgoose 6mo ago
      The latest dedibox from Scaleway.
      - miyuru 6mo ago
        Did you at least report it to scaleway, so they can fix the issue?
        speedgoose 6mo ago
        No, I did not bother because I don’t use IPv6 and I don’t plan to use it anytime soon. Reporting an issue usually involves some effort, and the support may decide to follow up even if I say that I don’t need a fix. It’s better if someone who cares about IPv6 reports it.
      - MaKey 6mo ago
        Here is the documentation from Scaleway on IPv6: https://www.scaleway.com/en/docs/dedibox-ipv6/quickstart/ https://www.scaleway.com/en/docs/dedibox-ipv6/quickstart/ The first step is to request an IPv6 prefix. Did you do that?
        speedgoose 6mo ago
        I did not read this documentation and I did not request a prefix. Thanks for the hint. IPv4 worked without any required action so I moved on. I wanted to use this example for my frustrations toward IPv6.

MaKey 6mo ago

You could have spent a bit of time on debugging the issue. This would have been a great learning opportunity.

Hackbraten 6mo ago
It's supposed to Just Work on clean and rescue systems. Otherwise, it's a regression with respect to v4. The fact that it doesn't work is evidence that someone has been doing something wrong. The user at the receiving end of this clusterfuck is not that someone.
speedgoose 6mo ago
I agree, but debugging IPv6 issues is pretty far down on the list of things I want to learn.
- MaKey 6mo ago
  Which european cloud provider is it?
  - speedgoose 6mo ago
    The latest dedibox from Scaleway.
    - miyuru 6mo ago
      Did you at least report it to scaleway, so they can fix the issue?
      - speedgoose 6mo ago
        No, I did not bother because I don’t use IPv6 and I don’t plan to use it anytime soon. Reporting an issue usually involves some effort, and the support may decide to follow up even if I say that I don’t need a fix. It’s better if someone who cares about IPv6 reports it.
    - MaKey 6mo ago
      Here is the documentation from Scaleway on IPv6: https://www.scaleway.com/en/docs/dedibox-ipv6/quickstart/ https://www.scaleway.com/en/docs/dedibox-ipv6/quickstart/ The first step is to request an IPv6 prefix. Did you do that?
      - speedgoose 6mo ago
        I did not read this documentation and I did not request a prefix. Thanks for the hint. IPv4 worked without any required action so I moved on. I wanted to use this example for my frustrations toward IPv6.