Your message dated Tue, 8 Jul 2014 14:49:53 -0400 with message-id <CABJRnBe79KnOpHKeka7x7be3OHkvSr6OaLHUw6-Tj7Y+4fB9UQ@mail.gmail.com> and subject line has caused the Debian Bug report #751788, regarding qa.d.o and other services on quantz are inaccessible from T-Mobile to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 751788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751788 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: "submit@bugs.debian.org" <submit@bugs.debian.org>
- Subject: qa.d.o and other services on quantz are inaccessible from T-Mobile
- From: Harlan Lieberman-Berg <H.LiebermanBerg@gmail.com>
- Date: Mon, 16 Jun 2014 12:51:56 -0400
- Message-id: <CABJRnBdT4BigguzKCOKAW2qdoFispWHQKX++KYYh2qEW0zhCOA@mail.gmail.com>
When you try to access any of the services hosted on quantz over the T-Mobile US cell network (specifically tested with p.qa.d.o and qa.d.o), you end up getting a 504 Gateway Timeout after an approximately 30 second wait.paultag and I both replicated this with different devices on T-Mobile. He took a look on quantz, and we don't see any errors in the error log, nor the relevant hits in the access log when a request is made from a T-Mobile device. It's as if some proxy server that T-Mobile is using is not able to reach quantz, or there's some strange content being sent around that's breaking somebody.
Let me know if I can help out with the debugging of this one.
Sincerely,
--Harlan Lieberman-Berg~hlieberman
--- End Message ---
--- Begin Message ---
- To: 751788-done@bugs.debian.org, "control@bugs.debian.org" <control@bugs.debian.org>
- Subject:
- From: Harlan Lieberman-Berg <hliebermanberg@gmail.com>
- Date: Tue, 8 Jul 2014 14:49:53 -0400
- Message-id: <CABJRnBe79KnOpHKeka7x7be3OHkvSr6OaLHUw6-Tj7Y+4fB9UQ@mail.gmail.com>
~hliebermanHarlan Lieberman-BergSincerely,You can do this by manipulating the APN records in your phone as per http://support.t-mobile.com/thread/57886. Then you will have full IPv6 connectivity, as well as being routed through different T-Mobile infrastructure for v4 that will not have problem reaching quantz.That being said, there appears to be a good workaround that provides other benefits. If you switch to the IPv6 infrastructure that T-Mobile provides, you no longer have any trouble reaching quantz et al.After checking with T-Mobile, it doesn't look like this issue is going to go away soon.tags -1 +wontfix +upstreamthanks
--
--- End Message ---