On Saturday, 7 July 2018 7:44:59 PM AEST Raphael Hertzog wrote:
> > is what I get when I run `mtr tracker.debian.org`:
> So this really looks like a network problem... and something that
> I have no control over as tracker.debian.org maintainer.
Fair enough but the problem is affecting official Debian service.
We should escalate to Debian network people then.
> This bug should thus be closed and you should get in touch with your
> network administrator.
No no no. My network administrator have nothing to do with that. According to
`mtr`, packet loss is happening one hop away from destination where
tracker.debian.org is hosted, on "bm-bl1.debian.org" which is on the same
subnet with tracker's host. That's on another continent from me, 13 hops
away.
That kind of problems are difficult to troubleshoot but it is affecting
Debian infrastructure where "tracker.debian.org" is hosted.
> Have you tried to figure out whether you have a forced/transparent proxy
> which is dropping the answer to some requests?
We don't have anything like that.
> Do the following commands work faster ?
>
> curl https://tracker.debian.org/static/css/dense.css
> or
> wget https://tracker.debian.org/static/css/dense.css
Yes they do work faster however it is not the same as browser requests.
Browser fetches few URLs concurrently and if it hits black hole with larger
packet(s) then in turn it may affect smaller requests. I guess something
happens during TLS negotiation which affects subsequent requests...
> Probably, but you're most likely not speaking to the right person.
I wish I knew the right person to speak to...
--
Regards,
Dmitry Smirnov.
---
The surest way to corrupt a youth is to instruct him to hold in higher
esteem those who think alike than those who think differently.
-- Friedrich Nietzsche
Attachment:
signature.asc
Description: This is a digitally signed message part.