search

NICMx / Jool

SIIT and NAT64 for Linux
GNU General Public License v2.0
326 stars 66 forks source link

Github is not available from IPv6 #190

Closed ydahhrk closed 3 years ago

ydahhrk commented 9 years ago

Yeah

ydahhrk commented 8 years ago

Update:

The old jool.mx is again offered as a fall-back workaround. It should be available both from IPv4 and IPv6.

jool.mx is still a little rough in that it can still take several days to reflect updates, so github.io is still preferred where available. Not really anymore.

Actually, for some reason jool.mx can't be accessed from some parts of the world via IPv6. It seems they have some routing/DNS problem they need to spot. This issue will remain open until it's sorted out.

ydahhrk commented 7 years ago

Actually, for some reason jool.mx can't be accessed from some parts of the world via IPv6. It seems they have some routing/DNS problem they need to spot. This issue will remain open until it's sorted out.

We're having trouble finding a source from which a failing traceroute can be performed.

Is there somebody out there being affected by this problem? Can somebody please provide an IPv6 traceroute?

Specifically, the problem is the warning being reported here:

http://validador.ipv6.br/index.php?site=www.jool.mx&lang=en http://ready.chair6.net/?url=www.jool.mx

pierky commented 7 years ago

I have ran some measurements using RIPE Atlas :

https://atlas.ripe.net/measurements/?search=jool.mx&status=&af=&kind=&age=

You can find a ping msm followed by a traceroute from those probes which didn't get a positive outcome from the previous ping.

Sorry, I haven't had time to analyze results yet :-/ Hope to do something more tomorrow.

ydahhrk commented 7 years ago

Thank you!

I can't really do much with the output, but sysadmins report that they're getting different errors and from different sources. Still trying to find a pattern.

Working...

toreanderson commented 7 years ago

This issue is resolved, as GitHub Pages / Fastly has enabled IPv6 for all *.github.io domains.

https://toreanderson.github.io/2017/07/30/update-ghp-fastly-ipv6.html

ydahhrk commented 7 years ago

This issue is resolved, as GitHub Pages / Fastly has enabled IPv6 for all *.github.io domains.

...................................................................... huh.

I was going to say that it's pretty odd that both validators report roughly the same warnings for both www.jool.mx and nicmx.github.io/Jool, but then I realized that, actually, they also report the same problems for www.google.com.

In fact, out of the three, jool.mx is the one that has the least warnings overall.

I'm really really stumped right now. I wonder if it has always been like this.

Not sure about closing this issue, but at least it's pretty obvious that it no longer deserves the critical tag.

Then again, nobody has ever actually complained about this...

ydahhrk commented 5 years ago

Update: github.io dropped IPv6 support. As a matter of fact, so did github.com, apparently. Since Jool releases are currently hosted on Github, and the Debian package is still queued, Jool is mostly unavailable from plain IPv6 right now. (The possible exceptions are the OpenWRT and openSUSE packages.)

Working...

ydahhrk commented 4 years ago

Though the repository and bug tracker are still unreachable from pure IPv6, the latest tarball is now hosted in jool.mx itself. So, IPv6-only users should be able to reach it.

I will therefore downgrade the severity of this bug.

cooperlees commented 3 years ago

FWIW I've been logging jobs for a long time through our Enterprise GitHub account for native IPv6 support on all GitHub services. Unfortunately they've never come back with a definitive road map of when and how this will actually occur. Sad times.

I plan to log another in early 2021 to see where they are at.

ydahhrk commented 3 years ago

Well, in truth, I suppose there's no point in keeping this issue open now. This is a Github bug, and hosting the latest release in jool.mx seems to be enough for Jool. And I don't see any other solutions.

Will include this issue in the 4.1.5 release and close it when that's out.

ydahhrk commented 3 years ago

4.1.5 released; closing.