4 ms·
You could have spent a bit of time on debugging the issue. This would have been a great learning opportunity.
by MaKey 5mo ago
You could have spent a bit of time on debugging the issue. This would have been a great learning opportunity.
- Hackbraten 5mo agoIt'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 5mo agoI agree, but debugging IPv6 issues is pretty far down on the list of things I want to learn.
- MaKey 5mo agoWhich european cloud provider is it?
- speedgoose 5mo agoThe latest dedibox from Scaleway.
- miyuru 5mo agoDid you at least report it to scaleway, so they can fix the issue?
- speedgoose 5mo agoNo, 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 5mo agoHere 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 5mo agoI 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.