turnkeylinux / tracker

TurnKey Linux Tracker
https://www.turnkeylinux.org
70 stars 16 forks source link

Add ipv6 support for archive.turnkeylinux.org #257

Open QueerCodingGirl opened 10 years ago

QueerCodingGirl commented 10 years ago

Our servers run on ipv6 only and it would be nice to use turnkey... but there is no AAAA dns record for archive.turnkeylinux.org.

please add ipv6 to your hosts, thanks.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

JedMeister commented 10 years ago

Technically this is probably a feature, but seeing as it should (at least theoretically) be a trivial adjustment and is a pretty important thing IMO I have marked it as a bug to hopefully ensure that it receives the priority it deserves...

QueerCodingGirl commented 10 years ago

Any news on this issue?! Still no one assigned... :(

lirazsiri commented 10 years ago

Hi Pascal,

Thanks for reporting this. Enabling IPv6 for the EC2 instance that hosts the archive is on my todo list. I hadn't realized there is anyone out there that doesn't have access to IPv4 on their servers.

Cheers, Liraz

On Sat, Sep 6, 2014 at 7:21 PM, Pascal Schneider notifications@github.com wrote:

Any news on this issue?! Still no one assigned... :(

— Reply to this email directly or view it on GitHub https://github.com/turnkeylinux/tracker/issues/257#issuecomment-54717102 .

QueerCodingGirl commented 10 years ago

Give this issue a high priority, please!

JedMeister commented 6 years ago

WTF?!? This still hasn't been done! It's 2018 and we still don't have IPv6 access to our package repo!

This needs fixing urgently!

QueerCodingGirl commented 6 years ago

Yes it does... since 2014!

JedMeister commented 6 years ago

FWIW, I queried @lirazsiri on this. He reported that he did indeed enable it at some point (circa late 2014; not that long after his last post apparently). But there were some unintended consequence (not sure what they were?) so it got disabled again...

I have asked for further clarification and have noted, that this will need to be resolved at some point. So if not now, when? We'll see...

OnGle commented 5 years ago

Ping @JedMeister could I get a status update on this?

JedMeister commented 5 years ago

Apologies on the radio silence on this. Liraz has moved off to another project (he's still involved in TurnKey but not so actively). I'll follow up internally and at least get some clarification on why this hasn't moved. Frankly in late 2018 it's a bit embarrassing that IPv6 isn't available for our repo...

Duckbuster commented 4 years ago

Was experimenting with proxmox and turnkey lxc's. Was gonna do ipv6 only lxc's so I ran into this issue as well.

Please do a check on why this hasn't happened already, and what the issue was exactly.

Thank you in advance!

JedMeister commented 4 years ago

FWIW, I've just sent out another message asking why this hasn't happened yet and asking for clarification on what issues there might be and/or if there is someway that I can assist push this forward...

JedMeister commented 4 years ago

Ok, so I now understand the issue a bit better. I think I have a workaround, but unfortunately, I don't yet have the spare cycles to test and/or implement it. The (upcoming and well overdue) v16.0 release is my current priority (currently in RC but stable should be released really soon). Hopefully once the dust settles on that, I will be able to circle back to this and do some testing...

OnGle commented 3 years ago

@JedMeister what's the status on this?

I re-added critical label because this, if still an issue is actively making it impossible for users to use turnkeylinux and has done so for the last 7 years. I'm grudgingly moving this to 17.0 as 16.1 has long past but I heavily suggest we put the effort into fixing this as a top priority.

QueerCodingGirl commented 3 years ago

Would be great... i am still waiting on this one^^ And right now a mayor german hoster (Hetzner) has announced a massive price change for ipv4 addresses. There will be an increased need for german turnkey users to get this fixed.

OnGle commented 2 years ago

@alonswartz I know you've got a lot on your plate atm, but any chance we could get this fixed before 17 stable? This issue has been here for 8 years and afaik you're the only one who can handle this.

codedbreeze commented 2 years ago

Hi, any updates on IPv6 support? Or is it entirely impossible to implement?

JedMeister commented 2 years ago

Hi, any updates on IPv6 support? Or is it entirely impossible to implement?

Unfortunately it's not currently possible with our infrastructure set up. We do have a workaround designed, but we just haven't had the spare cycles to implement it.

I hope to circle back to this once we (finally) complete the v17.x release.

codedbreeze commented 2 years ago

Thanks for the update @JedMeister. Please be sure to provide an update when the workaround is finally implemented.

JedMeister commented 1 year ago

This is still unresolved... It got to the top of my todo list, then I had to reprioritise to focus on v18.0. Once v18.0 is released, I hope to circle back to this one...