The Mirror Redirection System fails with Argentina

[Luis Marmisa]

The mirror redirection system http://mirrordirector.raspbian.org/ fails at least to users of Argentina.

They are unable to update their systems except if they select a Raspbian mirror server.

pi@raspberrypi:~ $ ping -c4 mirrordirector.raspbian.org
PING mirrordirector.raspbian.org (5.153.225.207) 56(84) bytes of data.

--- mirrordirector.raspbian.org ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3003ms

pi@raspberrypi:~ $ ping -c4 5.153.225.207
PING 5.153.225.207 (5.153.225.207) 56(84) bytes of data.

--- 5.153.225.207 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3005ms

pi@raspberrypi:~ $ wget mirrordirector.raspbian.org -O /dev/null
--2016-10-08 17:21:42-- http://mirrordirector.raspbian.org/
Resolviendo mirrordirector.raspbian.org (mirrordirector.raspbian.org)... 5.153.225.207, 2001:41c9:1:3ce::11
Conectando con mirrordirector.raspbian.org (mirrordirector.raspbian.org)[5.153.225.207]:80... falló: Expiró el tiempo de conexión.
Conectando con mirrordirector.raspbian.org (mirrordirector.raspbian.org)[2001:41c9:1:3ce::11]:80... falló: La red es inaccesible.

pi@raspberrypi:~ $ traceroute mirrordirector.raspbian.org
traceroute to mirrordirector.raspbian.org (5.153.225.207), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 2.340 ms 5.552 ms 5.888 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 137-161-89-200.fibertel.com.ar (200.89.161.137) 28.693 ms 81-161-89-200.fibertel.com.ar (200.89.161.81) 10.577 ms 137-161-89-200.fibertel.com.ar (200.89.161.137) 15.205 ms
7 150-165-89-200.fibertel.com.ar (200.89.165.150) 19.196 ms 12.386 ms 86-165-89-200.fibertel.com.ar (200.89.165.86) 14.211 ms
8 xe1-0-0.baires3.bai.seabone.net (195.22.220.56) 13.253 ms 13.472 ms 13.729 ms
9 ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 40.472 ms et4-1-0.sanpaolo8.spa.seabone.net (195.22.219.75) 40.801 ms ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 39.861 ms
10 et10-1-0.sanpaolo8.spa.seabone.net (195.22.219.145) 38.722 ms ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 40.171 ms et10-1-0.sanpaolo8.spa.seabone.net (195.22.219.145) 37.937 ms
11 ntt-verio.sanpaolo8.spa.seabone.net (149.3.181.65) 40.431 ms 41.003 ms 43.776 ms
12 ae-4.r24.nycmny01.us.bb.gin.ntt.net (129.250.2.227) 155.913 ms 151.216 ms 156.153 ms
13 ae-9.r24.londen12.uk.bb.gin.ntt.net (129.250.2.19) 228.913 ms 232.407 ms 230.105 ms
14 ae-6.r00.londen10.uk.bb.gin.ntt.net (129.250.4.21) 217.197 ms 226.218 ms 219.353 ms
15 81.25.207.214 (81.25.207.214) 223.427 ms 228.320 ms 220.357 ms
16 te1-5.cr2.yrk.bytemark.co.uk (91.223.58.144) 248.397 ms 246.958 ms 247.937 ms
17 po1.ar2.dc1.yo26.yrk.bytemark.co.uk (91.223.58.33) 267.434 ms 254.230 ms 254.210 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

They do not suffer any problem with other raspbian.org servers:

pi@raspberrypi:~ $ ping -c4 raspbian.org
PING raspbian.org (5.153.225.206) 56(84) bytes of data.
64 bytes from raspbian.org (5.153.225.206): icmp_seq=1 ttl=40 time=248 ms
64 bytes from raspbian.org (5.153.225.206): icmp_seq=2 ttl=40 time=247 ms
64 bytes from raspbian.org (5.153.225.206): icmp_seq=3 ttl=40 time=244 ms
64 bytes from raspbian.org (5.153.225.206): icmp_seq=4 ttl=40 time=249 ms

--- raspbian.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 244.078/247.427/249.799/2.179 ms

pi@raspberrypi:~ $ ping -c4 5.153.225.206
PING 5.153.225.206 (5.153.225.206) 56(84) bytes of data.
64 bytes from 5.153.225.206: icmp_seq=1 ttl=40 time=245 ms
64 bytes from 5.153.225.206: icmp_seq=2 ttl=40 time=248 ms
64 bytes from 5.153.225.206: icmp_seq=3 ttl=40 time=252 ms
64 bytes from 5.153.225.206: icmp_seq=4 ttl=40 time=250 ms

--- 5.153.225.206 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 245.845/249.534/252.869/2.629 ms

pi@raspberrypi:~ $ wget raspbian.org -O /dev/null
--2016-10-08 17:24:30-- http://raspbian.org/
Resolviendo raspbian.org (raspbian.org)... 5.153.225.206, 2001:41c9:1:3ce::10
Conectando con raspbian.org (raspbian.org)[5.153.225.206]:80... conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud: 10149 (9,9K) [text/html]
Grabando a: “/dev/null”

/dev/null 100%[=====================>] 9,91K --.-KB/s en 0,005s

2016-10-08 17:24:30 (2,14 MB/s) - “/dev/null” guardado [10149/10149]

pi@raspberrypi:~ $ traceroute raspbian.org
traceroute to raspbian.org (5.153.225.206), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 2.427 ms 3.797 ms 3.980 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 137-161-89-200.fibertel.com.ar (200.89.161.137) 33.456 ms 133-161-89-200.fibertel.com.ar (200.89.161.133) 15.382 ms 145-161-89-200.fibertel.com.ar (200.89.161.145) 18.056 ms
7 150-165-89-200.fibertel.com.ar (200.89.165.150) 13.948 ms 16.291 ms 18.820 ms
8 xe1-1-1.baires3.bai.seabone.net (195.22.220.100) 22.591 ms 18.898 ms 18.827 ms
9 ae7.sanpaolo8.spa.seabone.net (195.22.219.17) 40.549 ms et4-1-0.sanpaolo8.spa.seabone.net (195.22.219.75) 38.315 ms ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 38.351 ms
10 ae7.sanpaolo8.spa.seabone.net (195.22.219.17) 40.745 ms 41.651 ms ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 41.033 ms
11 ntt-verio.sanpaolo8.spa.seabone.net (149.3.181.65) 40.776 ms 38.622 ms 50.788 ms
12 ae-4.r24.nycmny01.us.bb.gin.ntt.net (129.250.2.227) 161.745 ms 161.943 ms 164.224 ms
13 ae-9.r24.londen12.uk.bb.gin.ntt.net (129.250.2.19) 235.915 ms 238.906 ms 229.897 ms
14 ae-6.r00.londen10.uk.bb.gin.ntt.net (129.250.4.21) 225.476 ms 225.340 ms 217.697 ms
15 81.25.207.214 (81.25.207.214) 216.904 ms 216.269 ms 220.866 ms
16 te1-5.cr2.yrk.bytemark.co.uk (91.223.58.144) 237.583 ms 239.528 ms 237.570 ms
17 po1.ar2.dc1.yo26.yrk.bytemark.co.uk (91.223.58.33) 248.192 ms 256.956 ms 254.513 ms
18 raspbian.org (5.153.225.206) 247.970 ms 253.496 ms 252.069 ms
pi@raspberrypi:~ $

More information here:

https://www.raspberrypi.org/forums/viewtopic.php?p=1049704#p1049704

[peter green (plugwash)]

raspbian.org and mirrordirector.raspbian.org are two the same physical server on the same network. So the ability to traceroute to one but not the other is very strange.

Unfortunately I don't speak spanish so I can't easilly engage in the forum thread (in which it seems there are serveral people with different problems).

[peter green (plugwash)]

Even stranger is the fact that the trace reaches the router immediately before our server. All I can think of is that your ISP is blocking incoming traffic from the IP for some unknown reason.

[Luis Marmisa (lmarmisa)]

I (lmarmisa) helped to that guy (abe51) to solve his problem.

We have two very close public IP addresses: 5.153.225.206 (raspbian.org)
and 5.153.225.207 (mirrordirector.raspbian.org).

According to the commands ping and traceroute, the address 5.153.225.206
works fine but 5.153.225.207 does not reply anything to Buenos Aires. If
you look at the two traceroute commands, the step 17
po1.ar2.dc1.yo26.yrk.bytemark.co.uk (91.223.58.33) is reached in both
cases. But step 18 is different because mirrordirector do not send any
reply to Argentina. Why?. This is a mystery.

The problem is not temporary. That guy suffered it for a long time.

Do you think that the cause is a filter of the Argentinian ISP?. Is your
server mirrordirector.raspbian.org blacklisted?. Maybe, but it sounds very
odd.

In the other side, mirrordirector could have some kind of filter related to
certain IP ranges or even blacklists?. I do not know.

I recommended to abe51 to open a new thread when he needs to post a new
problem. So previous posts in the thread are not related with this issue.

I read frequently the forums and the Spanish forum is one of my preferred.
I have read several posts with similar problems related to updates but I
did not pay too much attention to them. This is the only that I followed in
detail. In general the update problems trend to be located at South America.

Thanks four you time.

Best regards,

Luis

On Wed, Oct 12, 2016 at 11:50 PM, peter green <email address hidden> wrote:

> Even stranger is the fact that the trace reaches the router immediately
> before our server. All I can think of is that your ISP is blocking
> incoming traffic from the IP for some unknown reason.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1632764
>
> Title:
> The Mirror Redirection System fails with Argentina
>
> Status in Raspbian:
> New
>
> Bug description:
> The mirror redirection system http://mirrordirector.raspbian.org/
> fails at least to users of Argentina.
>
> They are unable to update their systems except if they select a
> Raspbian mirror server.
>
> pi@raspberrypi:~ $ ping -c4 mirrordirector.raspbian.org
> PING mirrordirector.raspbian.org (5.153.225.207) 56(84) bytes of data.
>
> --- mirrordirector.raspbian.org ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3003ms
>
>
> pi@raspberrypi:~ $ ping -c4 5.153.225.207
> PING 5.153.225.207 (5.153.225.207) 56(84) bytes of data.
>
> --- 5.153.225.207 ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3005ms
>
>
> pi@raspberrypi:~ $ wget mirrordirector.raspbian.org -O /dev/null
> --2016-10-08 17:21:42-- http://mirrordirector.raspbian.org/
> Resolviendo mirrordirector.raspbian.org (mirrordirector.raspbian.org)...
> 5.153.225.207, 2001:41c9:1:3ce::11
> Conectando con mirrordirector.raspbian.org (mirrordirector.raspbian.org
> )[5.153.225.207]:80... falló: Expiró el tiempo de conexión.
> Conectando con mirrordirector.raspbian.org (mirrordirector.raspbian.org
> )[2001:41c9:1:3ce::11]:80... falló: La red es inaccesible.
>
>
> pi@raspberrypi...

[Luis Marmisa (lmarmisa)]

Take a look to this thread. That problem seems similar:

https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=125231

On Wed, Oct 12, 2016 at 11:50 PM, peter green <email address hidden> wrote:

> Even stranger is the fact that the trace reaches the router immediately
> before our server. All I can think of is that your ISP is blocking
> incoming traffic from the IP for some unknown reason.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1632764
>
> Title:
> The Mirror Redirection System fails with Argentina
>
> Status in Raspbian:
> New
>
> Bug description:
> The mirror redirection system http://mirrordirector.raspbian.org/
> fails at least to users of Argentina.
>
> They are unable to update their systems except if they select a
> Raspbian mirror server.
>
> pi@raspberrypi:~ $ ping -c4 mirrordirector.raspbian.org
> PING mirrordirector.raspbian.org (5.153.225.207) 56(84) bytes of data.
>
> --- mirrordirector.raspbian.org ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3003ms
>
>
> pi@raspberrypi:~ $ ping -c4 5.153.225.207
> PING 5.153.225.207 (5.153.225.207) 56(84) bytes of data.
>
> --- 5.153.225.207 ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3005ms
>
>
> pi@raspberrypi:~ $ wget mirrordirector.raspbian.org -O /dev/null
> --2016-10-08 17:21:42-- http://mirrordirector.raspbian.org/
> Resolviendo mirrordirector.raspbian.org (mirrordirector.raspbian.org)...
> 5.153.225.207, 2001:41c9:1:3ce::11
> Conectando con mirrordirector.raspbian.org (mirrordirector.raspbian.org
> )[5.153.225.207]:80... falló: Expiró el tiempo de conexión.
> Conectando con mirrordirector.raspbian.org (mirrordirector.raspbian.org
> )[2001:41c9:1:3ce::11]:80... falló: La red es inaccesible.
>
>
> pi@raspberrypi:~ $ traceroute mirrordirector.raspbian.org
> traceroute to mirrordirector.raspbian.org (5.153.225.207), 30 hops max,
> 60 byte packets
> 1 192.168.1.1 (192.168.1.1) 2.340 ms 5.552 ms 5.888 ms
> 2 * * *
> 3 * * *
> 4 * * *
> 5 * * *
> 6 137-161-89-200.fibertel.com.ar (200.89.161.137) 28.693 ms
> 81-161-89-200.fibertel.com.ar (200.89.161.81) 10.577 ms
> 137-161-89-200.fibertel.com.ar (200.89.161.137) 15.205 ms
> 7 150-165-89-200.fibertel.com.ar (200.89.165.150) 19.196 ms 12.386 ms
> 86-165-89-200.fibertel.com.ar (200.89.165.86) 14.211 ms
> 8 xe1-0-0.baires3.bai.seabone.net (195.22.220.56) 13.253 ms 13.472 ms
> 13.729 ms
> 9 ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 40.472 ms
> et4-1-0.sanpaolo8.spa.seabone.net (195.22.219.75) 40.801 ms
> ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 39.861 ms
> 10 et10-1-0.sanpaolo8.spa.seabone.net (195.22.219.145) 38.722 ms
> ae6.sanpaolo8.spa.seabone.net (195.22.219.3) 40.171 ms
> et10-1-0.sanpaolo8.spa.seabone.net (195.22.219.145) 37.937 ms
> 11 ntt-verio.sanpaolo8.spa.seabone.net (149.3.181.65) 40.431 ms 41.003
> ms 43.776 ms
> 12 ae-4.r24.nycmny01.us.bb.gin.ntt.net (129.250.2.227) 155.913 ms
> 151.216 ms 156.153 ms
> 13 ae-9.r24.londen12.uk.bb.gin.ntt.net (129.250.2.19) 228.913 ms
> 232.407 ms 230.105 ms
> 14 ae-6....

[peter green (plugwash)]

> We have two very close public IP addresses: 5.153.225.206 (raspbian.org)
and 5.153.225.207 (mirrordirector.raspbian.org).

Very close indeed. The two IPs are on the same server.

> In the other side, mirrordirector could have some kind of filter related to
certain IP ranges or even blacklists?. I do not know.

We aren't implementing anything like that on the server end.

> But step 18 is different because mirrordirector do not send any
reply to Argentina. Why?. This is a mystery.

My guess is that we are sending it but it's getting filtered out somewhere on the path from our server back to the end user.