cancel
Showing results for 
Search instead for 
Did you mean: 

Routing issues

Melancholie
Grafter
Posts: 451
Thanks: 1
Registered: ‎23-07-2013

Routing issues

Saving a few quid by using the Mothership's transit appears to not be too hot for reliability.
Tracing route to 136.147.58.27 over a maximum of 30 hops
  1    1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    23 ms    27 ms    15 ms  lo0-central10.ptw-ag02.plus.net [195.166.128.196]
  4    14 ms    14 ms    14 ms  link-b-central10.ptw-gw02.plus.net [212.159.2.150]
  5    13 ms    19 ms    66 ms  xe-0-2-0.ptw-cr02.plus.net [212.159.0.250]
  6    14 ms    16 ms    14 ms  195.99.126.182
  7    15 ms    15 ms    15 ms  core4-BE4.faraday.ukcore.bt.net [213.121.193.182]
  8    14 ms    15 ms    14 ms  peer2-et-8-3-0.faraday.ukcore.bt.net [62.6.201.169]
  9    14 ms    14 ms    15 ms  213.137.183.38
10    94 ms  117 ms    97 ms  166-49-208-148.eu.bt.net [166.49.208.148]
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
4 REPLIES
Community Veteran
Posts: 1,841
Thanks: 103
Fixes: 6
Registered: ‎21-01-2013

Re: Routing issues

Are you sure about that target IP address?
It doesn't give a reverse dns result and the tracert from the following site does not complete.
http://ping.eu/traceroute/
Community Veteran
Posts: 5,177
Thanks: 482
Fixes: 20
Registered: ‎10-06-2010

Re: Routing issues

The port checker on ping.eu indicates that ports 80 and 443 are open on 136.147.58.27, but a tcp traceroute also ends at 166.49.208.148.
[tt]# traceroute -q 1 -N 1 -T -p 80 136.147.58.27
traceroute to 136.147.58.27 (136.147.58.27), 30 hops max, 52 byte packets
1  gateway (192.168.0.1)  1.484 ms
2  lo0.13.central13.ptn-bng01.plus.net (195.166.128.231)  12.946 ms
3  irb.13.ptw-cr01.plus.net (84.93.249.49)  11.160 ms
4  195.99.126.138 (195.99.126.13Cool  12.058 ms
5  core4-BE4.faraday.ukcore.bt.net (213.121.193.182)  12.589 ms
6  peer2-et-10-3-0.faraday.ukcore.bt.net (62.6.201.171)  12.242 ms
7  213.137.183.34 (213.137.183.34)  12.613 ms
8  166-49-208-148.eu.bt.net (166.49.208.14Cool  97.234 ms
9  *
10  *
11  *
12  *
13  *
...[/tt]
Highlighted
Community Veteran
Posts: 2,286
Thanks: 109
Fixes: 4
Registered: ‎18-02-2013

Re: Routing issues

[tt]
sudo traceroute -q 1 -N 1 -T -p 80 136.147.58.27
traceroute to 136.147.58.27 (136.147.58.27), 30 hops max, 60 byte packets
1  192.168.0.254 (192.168.0.254)  2.025 ms
2  *
3  *
4  31.55.186.132 (31.55.186.132)  9.404 ms
5  195.99.127.54 (195.99.127.54)  8.876 ms
6  peer2-et-10-3-0.faraday.ukcore.bt.net (62.6.201.171)  8.622 ms
7  213.137.183.32 (213.137.183.32)  7.839 ms
8  166-49-208-123.eu.bt.net (166.49.208.123)  87.969 ms
9  *
10  xe-3-0-0.bbr2-dfw.net.salesforce.com (13.108.1.39)  129.573 ms
11  xe-3-0-1--dcr1-dfw.net.sfdc.net (136.147.60.11)  128.625 ms
12  *
13  *
14  *
15  136.147.58.27 (136.147.58.27)  123.606 ms
[/tt]
[tt]
./paping 136.147.58.27 -p 80 -c 4
paping v1.5.5 - Copyright (c) 2011 Mike Lovell
Connecting to 136.147.58.27 on TCP 80:
Connected to 136.147.58.27: time=128.63ms protocol=TCP port=80
Connected to 136.147.58.27: time=128.84ms protocol=TCP port=80
Connected to 136.147.58.27: time=127.87ms protocol=TCP port=80
Connected to 136.147.58.27: time=128.44ms protocol=TCP port=80
Connection statistics:
Attempted = 4, Connected = 4, Failed = 0 (0.00%)
Approximate connection times:
Minimum = 127.87ms, Maximum = 128.84ms, Average = 128.44ms
[/tt]
Melancholie
Grafter
Posts: 451
Thanks: 1
Registered: ‎23-07-2013

Re: Routing issues

Yes. Trying either via VPN or via mobile network the site is perfectly reachable.
I am quite sure of the IP address.
traceroute to 136.147.58.27 (136.147.58.27), 30 hops max, 60 byte packets
1  192.168.0.1 (192.168.0.1)  0.256 ms
2  *
3  lo0-central10.ptw-ag02.plus.net (195.166.128.196)  40.480 ms
4  link-b-central10.ptw-gw02.plus.net (212.159.2.150)  13.805 ms
5  xe-0-2-0.ptw-cr02.plus.net (212.159.0.250)  15.995 ms
6  195.99.126.182 (195.99.126.182)  14.572 ms
7  core3-te0-2-0-15.faraday.ukcore.bt.net (213.121.193.176)  15.039 ms
8  peer2-et-10-3-0.faraday.ukcore.bt.net (62.6.201.171)  14.615 ms
9  213.137.183.32 (213.137.183.32)  14.579 ms
10  t2c2-p0-2-0.cz-pra.eu.bt.net (166.49.208.121)  93.581 ms
11  *
12  *
13  *
telnet 136.147.58.27 443
Trying 136.147.58.27...
^C
telnet 136.147.58.27 80
Trying 136.147.58.27...
^C
Can also ping and traceroute using VPN.
No matter.