[Python-Dev] [Infrastructure] bugs.python.org not reachable in IPv6?

R. David Murray rdmurray at bitdance.com
Mon Nov 4 17:05:25 CET 2013


On Mon, 04 Nov 2013 16:34:46 +0100, Antoine Pitrou <antoine at python.org> wrote:
> On lun., 2013-11-04 at 16:09 +0100, M.-A. Lemburg wrote:
> > On 04.11.2013 11:01, Victor Stinner wrote:
> > > Hi,
> > > 
> > > bugs.python.org is still not responding on IPv6. Can someone please
> > > remove the AAAA record from python.org DNS, or fix the IPv6
> > > configuration?
> > > 
> > > It's an issue on my PC because my PC has IPv6 address and so it cannot
> > > reach bugs.python.org. wget is really slow because it tries first
> > > IPv6, but then falls back to IPv4. Firefox tries first IPv4 and so
> > > doesn't have the issue.
> > 
> > The infrastructure team cannot do anything about this, since
> > the tracker is hosted by Upfront Systems.
> > 
> > They are hosting the instance at Hetzner in Germany, which does
> > support IPv6.
> > 
> > Do we have someone with login permission for the server running
> > RoundUp ?
> 
> I think Ezio and Martin have access to the machine, but not necessarily
> root access; and, furthermore, the problem might be somewhere else on
> the network.
> 
> I think the best short-term measure is to disable the IPv6 resolution
> for bugs.python.org. Otherwise people will run in the same issue over
> and over again.

We have root, but I don't think that helps.

I currently see this:

eth0      Link encap:Ethernet  HWaddr 6c:62:6d:85:bb:7b  
          inet addr:46.4.197.70  Bcast:46.4.197.71  Mask:255.255.255.248
          inet6 addr: 2a01:4f8:131:2480::3/64 Scope:Global

so the problem appears to be a network issue (as far as I can see,
there's no firewall running on the box itself).  Disabling the AAA name
record until we get a response from upfront sounds like a good idea.
(I've added the upfront folks as nosy on the ticket Antoine opened
on the meta-tracker.)

--David


More information about the Python-Dev mailing list