This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Questions about network routing
- Previous message (by thread): [db-wg] Deployment of New RIPE Database Web Forms
- Next message (by thread): [db-wg] Questions about network routing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Zygimantas Surgailis
zlygis at gmail.com
Mon Aug  8 06:54:58 CEST 2011
Hello,
Hope someone can help me.
For few months now I've noticed the increased responce time from some
of my servers in German datacenters (Lithuania -> Germany) from one
Internet provider (this problem doesnt occur when using other
providers). Also, the problem occurs only with servers collocated in
Hetzner DC.
For example traffic to hetzner.de goes through Russia:
Tracing route to hetzner.de [213.133.107.227]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    <1 ms    <1 ms    <1 ms  XXXXX.meganet.lt [XXXXXX]
  3    <1 ms    <1 ms    <1 ms  88.223.0.254
  4     1 ms     1 ms     2 ms  88.223.0.157
  5    <1 ms    <1 ms    <1 ms  80.232.131.233
  6     5 ms     5 ms     4 ms  87.110.223.237
  7     6 ms     7 ms     7 ms  195.122.0.133
  8     7 ms     7 ms     7 ms  195.122.0.121
  9    21 ms    21 ms    21 ms  92.50.199.29
 10    98 ms   111 ms    98 ms
xe-1-0-0.frkt-ar2.intl.ip.rostelecom.ru [87.226.133.110]
 11    76 ms    76 ms    76 ms  decix2-gw.hetzner.de [80.81.193.164]
 12    83 ms    84 ms    84 ms  hos-bb1.juniper2.fs.hetzner.de [213.239.240.243]
 13    81 ms    82 ms    81 ms  hos-tr3.ms-ex3k1.rz11.hetzner.de
[213.239.236.99]
 14    81 ms    80 ms    80 ms  www.hetzner.de [213.133.107.227]
Trace complete.
But traffic to e-shelter.de goes directly to Germany:
Tracing route to e-shelter.de [91.208.160.80]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    <1 ms    <1 ms    <1 ms  XXXXXXX.meganet.lt [XXXXX]
  3    <1 ms    <1 ms    <1 ms  88.223.0.254
  4     *        1 ms     1 ms  88.223.0.157
  5    <1 ms    <1 ms    <1 ms  80.232.131.233
  6     5 ms     5 ms     5 ms  87.110.223.78
  7    13 ms    13 ms    13 ms  xe-0-2-0-301.stk30.ip4.tinet.net [77.67.66.133]
  8    78 ms    44 ms    44 ms  xe-0-0-0.fra60.ip4.tinet.net [89.149.185.105]
  9    46 ms    46 ms    46 ms
ge-0-1-0.pr1.k90.fra.de.eurotransit.net [213.200.86.50]
 10    39 ms    39 ms    39 ms  adacor.demarc.eurotransit.net [82.96.89.182]
 11    39 ms    39 ms    39 ms  91-208-160-80.static.ip.adacor.net
[91.208.160.80]
 12    45 ms    40 ms    39 ms  91-208-160-80.static.ip.adacor.net
[91.208.160.80]
Trace complete.
I've contacted Latvian telecom ant here is their answer:
"Path  via Rpstelecom is shortest by AS-Path lenght.
Router: az8-crs
Command: show bgp 213.133.107.227
Mon Jul 25 09:06:29.824 EEST
BGP routing table entry for 213.133.96.0/19
Versions:
  Process           bRIB/RIB  SendTblVer
  Speaker          132081071   132081071
Last Modified: Jul  5 00:42:25.785 for 2w6d
Paths: (5 available, best #3)
  Advertised to update-groups (with more than one peer):
    0.5 0.14 0.17
  Advertised to peers (in unique update groups):
    195.122.0.5
  Path #1: Received by speaker 0
  Not advertised to any peer
  3216 13030 24940, (aggregated by 24940 213.133.96.7)
    62.231.5.217 from 62.231.5.217 (194.67.0.95)
      Origin IGP, localpref 90, weight 40, valid, external, group-best
      Received Path ID 0, Local Path ID 0, version 0
      Community: 12578:100 12578:3216
  Path #2: Received by speaker 0
  Not advertised to any peer
  3257 13030 24940, (aggregated by 24940 213.133.96.7)
    77.67.67.89 from 77.67.67.89 (213.200.87.15)
      Origin IGP, metric 170, localpref 100, weight 40, valid,
external, group-best
      Received Path ID 0, Local Path ID 0, version 0
      Community: 12578:100 12578:3257
  Path #3: Received by speaker 0
  Advertised to update-groups (with more than one peer):
    0.5 0.14 0.17
  Advertised to peers (in unique update groups):
    195.122.0.5
  12389 24940, (aggregated by 24940 213.133.96.10)
    92.50.199.29 from 92.50.199.29 (87.226.134.132)
      Origin IGP, localpref 110, weight 40, valid, external, best, group-best
      Received Path ID 0, Local Path ID 1, version 132081071
      Community: 12578:300 12578:12389 24940:24940
  Path #4: Received by speaker 0
  Not advertised to any peer
  3249 13030 24940, (aggregated by 24940 213.133.96.7)
    195.250.170.49 from 195.250.170.49 (84.50.255.90)
      Origin IGP, localpref 100, weight 40, valid, external, group-best
      Received Path ID 0, Local Path ID 0, version 0
      Community: 12578:100 12578:3249
  Path #5: Received by speaker 0
  Not advertised to any peer
  3320 3320 3320 24940 24940, (aggregated by 24940 213.133.96.10)
    217.243.219.117 from 217.243.219.117 (194.25.5.230)
      Origin IGP, localpref 100, weight 40, valid, external, group-best
      Received Path ID 0, Local Path ID 0, version 0
      Community: 12578:100 12578:3320
My knowledge is limited, so I'm not sure what should I do next, whom
should I contact?
Thank You for any help in advance.
- Previous message (by thread): [db-wg] Deployment of New RIPE Database Web Forms
- Next message (by thread): [db-wg] Questions about network routing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]