Re: wiki access

Hi list,

I think this rather has to do something with routing.

We have 2 locations in which we're unable to access the Wiki server and o=
ne location in which we are=20
able to connect to it. To make things funny the one location which is abl=
e to connect to the wiki=20
server uses the same ADSL provider as one location which isn't able to co=
nnect to the wiki server=20
(Planet.nl, a dutch ADSL provider). The difference between the two locati=
ons is the subnet in which=20
they are connected to the ISP The route of these two locations is complet=
ely the same to the other=20
side of the ocean.

Below are three traceroutes I perfomed. The first one is the working one,=
 the second and the third=20
aren't working:

Working location Helmond (Planet ADSL):
niels@stargate:~$ traceroute 66.105.113.115
traceroute to 66.105.113.115 (66.105.113.115), 30 hops max, 38 byte packe=
ts
  1  gw-helmond (10.10.10.1)  0.427 ms  0.294 ms  0.278 ms
  2  195.190.249.54 (195.190.249.54)  5.604 ms  4.788 ms  4.890 ms
  3  iawxsrt-dc2-bb21a.wxs.nl (213.75.1.1)  8.115 ms  14.623 ms  8.809 ms
  4  217.149.47.113 (217.149.47.113)  9.370 ms  9.081 ms  9.310 ms
  5  sl-bb21-ams-8-0.sprintlink.net (217.149.32.41)  8.679 ms  8.518 ms  =
9.155 ms
  6  sl-bb20-ham-14-0.sprintlink.net (213.206.129.50)  15.005 ms  15.142 =
ms  15.421 ms
  7  sl-bb20-cop-13-0.sprintlink.net (213.206.129.53)  21.886 ms  22.029 =
ms  21.489 ms
  8  sl-bb21-msq-10-0.sprintlink.net (144.232.19.29)  99.088 ms  99.620 m=
s  98.788 ms
  9  sl-bb27-rly-8-0.sprintlink.net (144.232.20.73)  103.402 ms  104.606 =
ms  103.694 ms
10  sl-bb26-rly-13-0.sprintlink.net (144.232.14.181)  104.000 ms  104.057=
 ms  104.462 ms
11  sl-st21-ash-10-0.sprintlink.net (144.232.20.148)  115.292 ms  105.051=
 ms  105.158 ms
12  sl-xocomm-13-0.sprintlink.net (144.223.246.114)  98.874 ms  98.820 ms=
  99.062 ms
13  p5-0-0.RAR2.Washington-DC.us.xo.net (65.106.3.137)  99.798 ms  99.828=
 ms  99.607 ms
14  p7-0-0.MAR2.Washington5-DC.us.xo.net (65.106.3.206)  101.121 ms  100.=
477 ms  100.696 ms
15  fe5-0.CLR2.Washington5-DC.us.xo.net (64.1.7.212)  313.161 ms  264.218=
 ms  141.959 ms
16  ip66-105-113-113.z113-105-66.customer.algx.net (66.105.113.113)  106.=
846 ms  104.026 ms  103.726

Non working customer Location Weert (Planet ADSL):
niels@atlas:~$ traceroute 66.105.113.115
traceroute to 66.105.113.115 (66.105.113.115), 30 hops max, 38 byte packe=
ts
  1  vpn-router (192.168.2.1)  1.474 ms  0.834 ms  1.215 ms
  2  195.190.245.64 (195.190.245.64)  7.099 ms  6.122 ms  6.229 ms
  3  iawxsrt-dc2-bb21a.wxs.nl (213.75.1.1)  12.473 ms  9.912 ms  10.351 m=
s
  4  217.149.47.113 (217.149.47.113)  10.719 ms  10.007 ms  10.096 ms
  5  sl-bb21-ams-8-0.sprintlink.net (217.149.32.41)  10.347 ms  10.317 ms=
  10.228 ms
  6  sl-bb20-ham-14-0.sprintlink.net (213.206.129.50)  16.719 ms  16.654 =
ms  16.723 ms
  7  sl-bb20-cop-13-0.sprintlink.net (213.206.129.53)  24.213 ms  23.535 =
ms  22.844 ms
  8  sl-bb21-msq-10-0.sprintlink.net (144.232.19.29)  100.669 ms  100.756=
 ms  100.543 ms
  9  sl-bb27-rly-8-0.sprintlink.net (144.232.20.73)  135.774 ms  210.895 =
ms  149.464 ms
10  sl-bb26-rly-13-0.sprintlink.net (144.232.14.181)  105.969 ms  105.918=
 ms  106.001 ms
11  sl-st21-ash-10-0.sprintlink.net (144.232.20.148)  107.411 ms  107.836=
 ms  107.478 ms
12  sl-xocomm-13-0.sprintlink.net (144.223.246.114)  100.463 ms  100.398 =
ms  100.971 ms
13  p5-0-0.RAR1.Washington-DC.us.xo.net (65.106.3.133)  101.973 ms  101.9=
16 ms  101.960 ms
14  p7-2-0.MAR1.Washington5-DC.us.xo.net (65.106.3.202)  102.960 ms  102.=
366 ms  102.471 ms
15  fe0-0.CLR2.Washington5-DC.us.xo.net (64.1.7.196)  102.700 ms  102.823=
 ms  102.670 ms
16  ip66-105-113-113.z113-105-66.customer.algx.net (66.105.113.113)  106.=
288 ms  105.753 ms  106.157

Non working location Budel (Wannadoo ADSL):
niels@goliath:~$ traceroute 66.105.113.115
traceroute to 66.105.113.115 (66.105.113.115), 30 hops max, 38 byte packe=
ts
  1  gw-budel (10.10.10.201)  0.531 ms  0.447 ms  0.430 ms
  2  195.190.244.197 (195.190.244.197)  10.133 ms  7.077 ms  8.879 ms
  3  G3-2-22.cr1-asd5.nl.euro.net (194.134.180.37)  27.593 ms  8.870 ms  =
9.599 ms
  4  10GE1-2.cr1-asd5.nl.euro.net (194.134.161.1)  16.527 ms  11.448 ms  =
9.397 ms
  5  Ge9-0.AMSBB2.Amsterdam.opentransit.net (193.251.252.133)  14.991 ms =
 21.584 ms  10.069 ms
  6  P1-0.NYKCR2.New-york.opentransit.net (193.251.243.85)  90.853 ms  94=
.811 ms  89.930 ms
  7  P6-0.NYKBB3.New-york.opentransit.net (193.251.241.238)  90.065 ms  9=
4.821 ms  90.122 ms
  8  p3-2.IR1.NYC-NY.us.xo.net (206.111.13.9)  89.389 ms  95.314 ms  89.6=
55 ms
  9  p5-0-0.RAR2.NYC-NY.us.xo.net (65.106.3.41)  113.479 ms  95.579 ms  9=
0.333 ms
10  p6-0-0.RAR1.Washington-DC.us.xo.net (65.106.0.2)  96.532 ms  100.179 =
ms  96.059 ms
11  p7-2-0.MAR1.Washington5-DC.us.xo.net (65.106.3.202)  96.334 ms  101.6=
13 ms  96.283 ms
12  fe0-0.CLR2.Washington5-DC.us.xo.net (64.1.7.196)  97.233 ms  101.948 =
ms  135.454 ms
13  ip66-105-113-113.z113-105-66.customer.algx.net (66.105.113.113)  102.=
955 ms  105.365 ms  101.199

The difference between the two Planet ISP connections is after hop 12 whe=
re our customer is routed=20
different through hops 13 and 14. Hop 14 in the non working location is t=
he same hop as hop 11 in=20
the other non working location.

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.

We solved this by routing traffic for the Wiki through our working locati=
on, but this is of course=20

not an ideal solution ;-)


Greetings Niels
CareWorks ICT Services
The Netherlands

Pierre Raoul wrote:

>>>With=20
>>>   telnet 66.105.113.115 80
>>>I got=20
>>>   Impossible d'ouvrir une connexion =E0 l'h=F4te sur le port 50:=20
>>>Echec lors de la connexion
>>>     (Unable to connect to the host with port 50: Failled to connect)
>>
>>This probably is the smoking gun.  Something is changing the port 80 to=
 port
>>50.  I'd look for that.
>=20
>=20
> Oops! Sorry... It's port 80 in the error message, indeed!
>=20
> Pierre