search

Icinga / icinga-packaging

Packaging documentation and issues for the official Icinga repository
https://packages.icinga.com
44 stars 15 forks source link

packages.icinga.com / ipv6 #93

Open jklippel opened 6 years ago

jklippel commented 6 years ago

Any chance that packages.icinga.com will get a ipv6 address in the near future? Using packages on a ipv6 only hosts would be much easier.

motp commented 6 years ago

Actually, IPv6 is the new default. The IANA Unallocated IPv4 Address Pool has been exhausted since 03-Feb-2011, that's more than 7 years back.

So you should be moving. NOW.

jenslink commented 6 years ago

It depends on the entire infrastructure hosting the Icinga servers.

Then lets assume that the infrastructure is rather old and should be replaced anyway. The alternative would be people ignoring reality for quite some time.

BTW: May I quote you in my presentation at the next RIPE meeting in October? No worries you'll be in good company, including github. sourceforge, twitter.

jenslink commented 4 years ago

After almost 1.5 years: Any news on this topic? Why is it taking so long and do you need any help?

nbuchwitz commented 4 years ago

https://packages6.icinga.com/

thtomate commented 4 years ago

packages.icinga.com:443 still refuses the connection

motp commented 4 years ago

https://packages6.icinga.com/

Why two different names? Why not just packages.icinga.com as a dualstack server?

andreaso commented 3 years ago

Status on https://packages6.icinga.com/?

Connecting to its IPv6 address 2a02:ed80:0:3::2f there is a TLS connection established, followed by a 504 Gateway Time-out.

ekohl commented 3 years ago

I get 100% packet loss on ping and timeouts on http(s).

bobapple commented 3 years ago

the domain packages6.icinga.com was our first approach to test IPv6 support for our repositories. Since our hoster officially does not provide IPv6 support we were happy to be allowed to test it with them.

Unfortunately, as you figured out already, this setup never left the testing environment for stability reasons.

Whenever we get fully working IPv6 we will provide it directly through packages.icinga.com. Right now it does not look promising however, since we’re the only ones requesting this at our hoster.

You may also follow this topic in the forum for a similar discussion: https://community.icinga.com/t/reachability-problems-for-packages6-icinga-com/5493/

ekohl commented 3 years ago

One possible solution is to use a CDN in front of packages.icinga.com. At the Foreman project we're very happy with the sponsoring Fastly provides for us as an open source project. It provides us dual stack access and caching. Take a look at https://www.fastly.com/open-source to see if it's anything that could work for you.

jenslink commented 3 years ago

the domain packages6.icinga.com was our first approach to test IPv6 support for our repositories. Since our hoster officially does not provide IPv6 support we were happy to be allowed to test it with them.

Looking at my calendar: It's almost 2021.

robert-scheck commented 3 years ago

Since our hoster officially does not provide IPv6 support we were happy to be allowed to test it with them.

Ehm?

Or what is meant by "hoster" exactly?

mlutfy commented 2 years ago

Today the repo returns "504 Gateway Time-out"

image

crza commented 2 years ago

Is there any progress or ETA on this issue? Even github and AWS has partial working IPv6 already.

And regarding hoster:

NETWAYS GmbH == Icinga GmbH Management, compare https://icinga.com/company/imprint and https://www.netways.de/en/legal/imprint/

jenslink commented 2 years ago

Totally forgot: Happy 4th birthday.

ekohl commented 2 years ago

As my birthday present of this ticket I set up an unofficial reverse proxy available only over IPv6: http://icinga.partial.solutions/

I make no guarantees about its uptime and any future. Use it at your own risk. In case of abuse, I may just take it private.

Right now 1 nameserver is being slow in updating so the AAAA record may not be available yet. Once it is, I can look at a Let's Encrypt certificate for HTTPS.