For the past three days I couldn’t reach any repos, I tried changing DNS servers, tried using IP address in repositories setting, nothing worked. Then tried to access download.opensure.org from the browser - nothing. All machines and devices connecting through my adsl/wifi are affected, so I ran traceroute and got this:
linux-k2rp:/home/stan # /usr/sbin/traceroute 195.135.221.134
traceroute to 195.135.221.134 (195.135.221.134), 30 hops max, 40 byte packets using UDP
1 192.168.2.1 (192.168.2.1) 0.297 ms 0.283 ms 0.217 ms
2 * * *
3 10.169.224.177 (10.169.224.177) 31.856 ms 31.375 ms 34.983 ms
4 119-46-176-109.static.asianet.co.th (119.46.176.109) 30.932 ms 31.292 ms 31.400 ms
5 61-91-210-66.static.asianet.co.th (61.91.210.66) 31.776 ms 30.884 ms 30.820 ms
6 203-144-144-27.static.asianet.co.th (203.144.144.27) 31.368 ms 31.467 ms 31.111 ms
7 61-91-210-1.static.asianet.co.th (61.91.210.1) 32.514 ms 32.626 ms 32.802 ms
8 TIG-Net25-85.trueintergateway.com (122.144.25.85) 32.236 ms 34.951 ms 33.856 ms
9 SG-ICR-GS1-26-210.trueintergateway.com (122.144.26.210) 70.763 ms 73.382 ms 71.990 ms
10 TIG-Net242-34.trueintergateway.com (113.21.242.34) 68.752 ms 67.500 ms 66.075 ms
11 116.51.17.193 (116.51.17.193) 255.399 ms 254.957 ms 255.375 ms
12 as-1.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.5.20) 266.964 ms 265.867 ms 262.282 ms
13 as-1.r22.amstnl02.nl.bb.gin.ntt.net (129.250.4.65) 300.803 ms 299.703 ms 299.971 ms
14 as-2.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.119) 302.535 ms 302.022 ms 325.964 ms
15 as-0.r21.frnkge04.de.bb.gin.ntt.net (129.250.3.63) 324.874 ms 295.895 ms 295.025 ms
16 * * *
17 213.198.72.238 (213.198.72.238) 288.364 ms 287.103 ms 287.573 ms
18 gi3-17.r1.nue1.m-online.net (212.18.6.77) 314.970 ms 311.595 ms 310.494 ms
19 gi3-17.r1.nue1.m-online.net (212.18.6.77) 309.414 ms 308.327 ms 307.232 ms
20 GW-SUSE-NEFkom.241.nefkom.de (212.114.146.241) 295.949 ms 290.052 ms 290.045 ms
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
linux-k2rp:/home/stan #
If I try to access download.opensuse.org from my mobile phone which it works, I tried to trace it, too, and the route was completely different.
Is there any workaround? I have two issues with my notebook that I can’t even start to resolve without access to repositories.
Yeah… traceroute isn’t good for troubleshooting almost anything. Sure,
it shows you a route, but it may not even always be the route your IP
packets take (often is, but not always) and traceroute uses ICMP while
your FTP/HTTP (and most other) data will use IP… not treated the same by
firewalls, even routers (a lot of people block pings for (usually) bad
(security by obscurity) reasons) which makes traceroute/ping broken.
Traceroute now has a -T option, which uses TCP SYN on port 80 by default to try to connect to the target. This is more realistic for this purpose than a UDP trace.
Incidentally the options for traceroute are worth reading. You have your choice of ICMP, UDP/IP or TCP/IP trace.