On Tue, 6 Nov 2007, David Groep wrote:
> Hi Maarten, all,
>
> So the "local" problem is not limited to CNAF but also CERN. But:
> I have no problems whatsoever from Nikhef, and also not now from REUNA (Chile).
> I can happily use wget from both Nikhef an my laptop here in Chile and
> get the CRL.
>
> So, is there a DNS problem somewhere at both CERN and CNAF?
> Who else has this problem?
> Does your local desktop have a different DNS server than the one where you
> tried the wget?
I should have said my browser at _home_! :-)
> [...]
> davidg@xpsdavidg ~
> $ tracert gridca.hpcc.nectec.or.th
>
> Tracing route to www.hpcc.nectec.or.th [203.185.132.199]
> over a maximum of 30 hops:
>
> 1 1 ms 1 ms 1 ms 192.168.0.1
> 2 28 ms 7 ms 62 ms MyViNE.local.lan [192.168.123.1]
> 3 10 ms 10 ms * ar6sentel.cnt.entelchile.net [200.72.3.103]
> 4 10 ms 8 ms 8 ms gr1s.cnt.entelchile.net [200.72.5.1]
> 5 8 ms 9 ms 9 ms san1-entel-chile-1-cl.san.seabone.net [195.22.22
> 1.37]
> 6 248 ms 248 ms 248 ms mil14-mil50-racc1.mil.seabone.net [195.22.196.16
> 9]
> ...
>
At CERN:
-----------------------------------------------------------------------------
$ traceroute 203.185.132.199
traceroute to 203.185.132.199 (203.185.132.199), 30 hops max, 38 byte packets
1 l513-v-rftec-1-ip163 (128.142.198.1) 0.390 ms 0.292 ms 13.057 ms
2 l513-b-rftec-2-rl7 (194.12.138.9) 2.819 ms 0.365 ms *
3 b513-b-rfte6-2-sl1 (194.12.131.73) 10.753 ms 0.528 ms 0.522 ms
4 g513-e-rci76-1-pg2 (194.12.144.41) 1.248 ms 0.823 ms *
5 g513-e-rci76-1-fe1 (192.65.184.165) 1.053 ms 0.871 ms 0.865 ms
6 e513-e-rci76-1-pe1 (192.65.184.161) 1.206 ms 1.146 ms *
7 swice2-10ge-1-2.switch.ch (192.65.184.221) 1.137 ms 1.100 ms 1.105 ms
8 switch.rt1.gen.ch.geant2.net (62.40.124.21) 1.143 ms 1.141 ms *
9 so-7-2-0.rt1.fra.de.geant2.net (62.40.112.22) 9.282 ms 9.227 ms 9.215 ms
10 sg-so-04.bb-v4.noc.tein2.net (202.179.249.13) 205.154 ms 205.109 ms 205.139 ms
11 th.pr-v4.noc.tein2.net (202.179.249.30) 227.539 ms 227.428 ms 227.612 ms
12 202.29.12.6 (202.29.12.6) 227.433 ms 263.078 ms 227.493 ms
Icmp checksum is wrong
13 192.150.250.10 (192.150.250.10) 232.905 msIcmp checksum is wrong
228.545 msIcmp checksum is wrong
233.000 ms
14 * * *
15 * * *
16 * *Icmp checksum is wrong
*
Icmp checksum is wrong
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * *Icmp checksum is wrong
*
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
-----------------------------------------------------------------------------
I will ask our network experts.
|