Re: Re: wiki access

N. Klomp wrote:

> I think this rather has to do something with routing.
[...]
> Non working location Budel (Wannadoo ADSL):
[...]
> So my guess is that traffic is somewhere filtered between that hop=20
> (p7-2-0.MAR1.Washington5-DC.us.xo.net) and the final destination.
>=20
> We solved this by routing traffic for the Wiki through our=20
> working location, but this is of course=20
>=20
> not an ideal solution ;-)

Yes.

In my case, with Wanadoo ADSL, I got:
tracert 66.105.113.115
D=E9termination de l'itin=E9raire vers ip66-105-113-115.z113-105-66.custo=
mer.algx.net [66.105.113.115] avec un maximum de 30 sauts :
  1    <1 ms    <1 ms    <1 ms  FIXE.mshome.net [192.168.0.1]=20
  2    68 ms    62 ms    62 ms  bsstl151-net1Lo3.francetelecom.net [193.2=
53.171.31]=20
  3    64 ms    62 ms    62 ms  10.224.32.148=20
  4    60 ms    62 ms    62 ms  pos12-0.nrsta104.Paris.francetelecom.net =
[193.252.159.34]=20
  5    61 ms    62 ms    62 ms  pos13-3.ntsta202.Paris.francetelecom.net =
[193.252.103.50]=20
  6    57 ms    62 ms    62 ms  193.251.126.58=20
  7   141 ms   140 ms   140 ms  P12-0.NYKCR3.New-york.opentransit.net [19=
3.251.241.134]=20
  8   143 ms   140 ms   140 ms  P7-0.NYKBB3.New-york.opentransit.net [193=
.251.241.242]=20
  9   145 ms   140 ms   140 ms  p3-2.IR1.NYC-NY.us.xo.net [206.111.13.9]=20
 10   137 ms   140 ms   140 ms  p5-0-0.RAR2.NYC-NY.us.xo.net [65.106.3.41=
]=20
 11   139 ms   140 ms   140 ms  p6-0-0.RAR1.Washington-DC.us.xo.net [65.1=
06.0.2]=20
 12   141 ms   140 ms   140 ms  p7-2-0.MAR1.Washington5-DC.us.xo.net [65.=
106.3.202]=20
 13   159 ms   140 ms   140 ms  fe0-0.CLR2.Washington5-DC.us.xo.net [64.1=
.7.196]=20
 14   156 ms   155 ms   140 ms  ip66-105-113-113.z113-105-66.customer.alg=
x.net [66.105.113.113]=20

with, at step 12, the same p7-2-0.MAR1.Washington5-DC.us.xo.net

Tomorrow, I will check with an other provider.

Pierre