Re: security.debian.org
On Monday, 2004-02-09 at 20:38:37 +0000, Neil McGovern wrote:
> On Mon, Feb 09, 2004 at 06:17:01PM +0100, Konstantin Filtschew wrote:
> > security.debian.org seems to be down
> neil@giraffe:~$ ping security.debian.org
> PING security.debian.org (130.89.175.33): 56 data bytes
> 64 bytes from 130.89.175.33: icmp_seq=0 ttl=51 time=68.8 ms
> 64 bytes from 130.89.175.33: icmp_seq=1 ttl=51 time=15.5 ms
> 64 bytes from 130.89.175.33: icmp_seq=2 ttl=51 time=15.0 ms
> 64 bytes from 130.89.175.33: icmp_seq=3 ttl=51 time=15.9 ms
> 64 bytes from 130.89.175.33: icmp_seq=4 ttl=51 time=15.5 ms
> --- security.debian.org ping statistics ---
> 5 packets transmitted, 5 packets received, 0% packet loss
> round-trip min/avg/max = 15.0/26.1/68.8 ms
When I received the mail, I immediately tried to ping it. No reply. I
still have the traceroute output from that time:
traceroute to security.debian.org (194.109.137.218), 30 hops max, 38 byte packets
1 firewally (172.17.0.7) 0.313 ms 0.265 ms 0.294 ms
2 217.5.98.173 (217.5.98.173) 41.572 ms 14.095 ms 16.924 ms
3 217.237.157.90 (217.237.157.90) 43.417 ms 13.360 ms 13.235 ms
4 m-ec1.M.DE.net.DTAG.DE (62.154.27.234) 43.712 ms 41.187 ms 13.722 ms
5 zcr2-so-5-2-0.Munich.cw.net (208.175.230.49) 43.801 ms 80.418 ms 13.694 ms
6 zcr1-ge-4-3-0-5.Munich.cw.net (208.175.230.253) 44.627 ms 14.025 ms 13.144 ms
7 bcr2-so-0-3-0.Amsterdam.cw.net (208.173.209.149) 44.844 ms 41.744 ms 41.494 ms
8 zcr2-so-1-0-0.Amsterdamamt.cw.net (208.173.209.198) 45.590 ms 40.869 ms 42.402 ms
9 zar1-ge-0-3-0.Amsterdamamt.cw.net (208.173.220.131) 46.314 ms zar1-ge-1-3-0.Amsterdamamt.cw.net (208.173.220.147) 325.519 ms 45.989 ms
10 kpn.Amsterdamamt.cw.net (208.173.212.154) 48.013 ms 45.763 ms 39.773 ms
11 0.so-1-3-0.xr1.d12.xs4all.net (194.109.5.101) 49.062 ms 67.547 ms 41.748 ms
12 0.so-3-0-0.cr1.d12.xs4all.net (194.109.5.58) 47.961 ms * 46.106 ms
13 * * *
14 * * *
Now the traceroute goes like this:
traceroute to security.debian.org (130.89.175.33), 30 hops max, 38 byte packets
1 firewally (172.17.0.7) 14.812 ms 0.293 ms 0.176 ms
2 217.5.98.173 (217.5.98.173) 14.354 ms 15.059 ms 16.953 ms
3 217.237.157.90 (217.237.157.90) 33.209 ms 12.916 ms 13.132 ms
4 f-ea1.F.DE.net.DTAG.DE (62.154.18.22) 47.707 ms 44.256 ms 19.434 ms
5 208.49.136.173 (208.49.136.173) 46.733 ms 17.878 ms 21.079 ms
6 pos12-0-2488M.cr1.FRA2.gblx.net (67.17.74.149) 38.589 ms 89.690 ms 26.491 ms
7 pos0-0-2488M.cr1.AMS2.gblx.net (67.17.64.90) 45.999 ms 39.470 ms 39.688 ms
8 so0-0-0-2488M.ar1.AMS1.gblx.net (67.17.65.230) 46.996 ms 38.572 ms 39.662 ms
9 SURFnet.ge-4-2-0.ar1.AMS1.gblx.net (67.17.162.206) 40.223 ms GigaSurf-Amsterdam.ge-2-1-0.ar1.AMS1.gblx.net (208.49.125.50) 39.632 ms 39.552 ms
10 P11-0.CR1.Amsterdam1.surf.net (145.145.166.33) 38.971 ms 71.401 ms 39.665 ms
11 PO1-0.CR2.Amsterdam1.surf.net (145.145.160.2) 39.699 ms 39.121 ms 39.690 ms
12 PO0-0.AR5.Enschede1.surf.net (145.145.163.14) 44.969 ms 44.032 ms 44.446 ms
13 utwente-router.Customer.surf.net (145.145.4.2) 44.232 ms 44.670 ms 43.218 ms
14 slagroom.snt.utwente.nl (130.89.175.33) 45.313 ms 82.717 ms 44.476 ms
You can see that this was probably not security.d.o being down, but some
router. the packets are taking a quite different path. Maybe U Twente
switched providers?
> Also see http://www.debian.org/News/2004/20040202
That's old news. The machine has been reactivated.
Lupe Christoph
--
| lupe@lupe-christoph.de | http://www.lupe-christoph.de/ |
| "Violence is the resort of the violent" Lu Tze |
| "Thief of Time", Terry Pratchett |
Reply to: