1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
<html><head><title>apt-panopticon explanations</title>
</head><body bgcolor="black" text="white"><h1>Welcome to the apt-panopticon explanations page.</h1>
<p>The purpose of this page is to try to explain everything shown on <a href="results/Report-web.html">the results page</a>,
so that the results page can link to the various parts for the curious.<p>
<hr><h1 id="IPv4">IPV4 tests</h1>
<p>Tests are tested over IPv4 if the mirror has IPv4 addresses.</p>
<hr><h1 id="IPv6">IPv6</h1>
<p>Tests are tested over IPv6 if the mirror has IPv6 addresses.</p>
<hr><h1 id="FTP">FTP tests</h1>
<p>The FTP tests have not been written yet.</p>
<hr><h1 id="HTTP">HTTP tests</h1>
<p>
</p>
<hr><h1 id="HTTPS">HTTPS tests</h1>
<p>
</p>
<hr><h1 id="RSYNC">rsync tests</h1>
<p>The RSYNC tests have not been written yet.</p>
<hr><h1 id="DNS-RR">DNS round robin tests</h1>
<p>The "DNS round robin" column lists the IP addresses for each mirror that is part of the DNS round robin, or DNS-RR.
The IPs are linked to the log for that specific IP when used via the DNS round robin, and is followed by the number of errors, warnings, or timeouts of any.
</p>
<hr><h1 id="Protocol">Protocol tests</h1>
<p>The Protocol test will give a warning if the protocol is changed during a redirect, HTTP -> HTTPS for example.
While apt HTTPS transport is now the default in Beowulf / Buster, not everyone with an older release will have that installed,
so redirecting HTTP to HTTPS will break apt for those people.
An error is given instead if that happens for mirrors in the DNS round robin.
Servers in the DNS round robin will not have the HTTPS certificate for the round robin domain, so redirecting to HTTPS for that is a mistake.
</p>
<hr><h1 id="URL-Sanity">URL sanity tests</h1>
<p>The URL sanity test replaces "/" in URLS with "///", to see if the mirror can cope with that.
This might happen due to a mis configuration by the apt user, but decent web servers should cope with that.
The result for a mirror that does not cope is a failed download for that use, so this is an error.
</p>
<hr><h1 id="Integrity">Integrity tests</h1>
<p></p>
<hr><h1 id="Updated">Updated tests</h1>
<p></p>
<hr><h1 id="Speed">Speed test</h1>
<p>The speed test tries to guess at a minimum and maximum speed range for each mirror.
It does this by measuring the reported speeds from the curl commands that actually download files.
Since apt-panopticon is trying hard to download everything from all mirrors all at the same time, this guess will be low.
Also, the computer running the apt-panopticon might have a network connection that is busy with other things.
Finally, the tested mirror may have a bigger network connection than the computer running the test, so wont show it's true maximum.
So take this speed measurement with a grain of salt, it's more of an indication, the <a href="apt-panopticon_cgp/index.php">full graphs</a> might be useful.
</p>
</body></html>
|
