12 Oct
2016
12 Oct
'16
9:48 a.m.
Hi,
I noticed that trinitydesktop.org and bugs.pearsoncomputing.net are
unreachable from time to time from my location in Austria.
What can I do to overcome this?
The traceroute is like this
traceroute -p 80 trinitydesktop.org
traceroute to trinitydesktop.org (192.119.205.246), 30 hops max, 60 byte
packets
1 fw.s-und-s.home (192.168.40.1) 0.819 ms 0.818 ms 1.178 ms
2 10.0.0.138 (10.0.0.138) 4.413 ms 4.435 ms 4.695 ms
3 178-191-255-254.adsl.highway.telekom.at (178.191.255.254) 22.098 ms
22.625 ms 23.649 ms
4 195.3.68.109 (195.3.68.109) 25.852 ms 25.867 ms 27.675 ms
5 lg1-1171.as8447.a1.net (195.3.64.2) 39.227 ms 40.015 ms 41.220 ms
6 ae7.fra29.ip4.gtt.net (141.136.99.57) 87.182 ms 85.773 ms 86.042 ms
7 et-3-1-0.was14.ip4.gtt.net (141.136.111.165) 128.943 ms 116.571 ms
116.858 ms
8 192.205.37.193 (192.205.37.193) 120.809 ms 119.968 ms 123.946 ms
9 cr1.wswdc.ip.att.net (12.122.113.38) 144.088 ms 144.326 ms 144.628 ms
10 cr2.sl9mo.ip.att.net (12.122.18.29) 147.708 ms 148.836 ms 149.094 ms
11 12.122.152.201 (12.122.152.201) 218.153 ms 218.149 ms 218.714 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
NetRange: 12.122.0.0 - 12.123.255.255 belongs to AT&T
Did AT&T outsourced to India :D
Thanks & regards
12 Oct
12 Oct
5:21 p.m.
New subject: [trinity-users] trinitydesktop.org and bugs.pearsoncomputing.net unreachable from time to time
On Wed October 12 2016 02:48:04 deloptes wrote:
I noticed that trinitydesktop.org and
bugs.pearsoncomputing.net are
unreachable from time to time from my location in Austria.
What can I do to overcome this?
The traceroute is like this
traceroute -p 80 trinitydesktop.org
Many firewalls will drop UDP 80. Try adding the -T flag.
--Mike
6:27 p.m.
New subject: [trinity-users] Re: trinitydesktop.org and bugs.pearsoncomputing.net unreachable from time to time
On Wed October 12 2016 10:24:17 deloptes wrote:
Mike Bird wrote:
The server is reachable (on TCP 80 but not UDP 80) by me from
five different test locations. Two of these use the same
ultimate route as your traffic via 12.122.152.201 e.g. [1].
This suggests that the problem lies in the routing of the
response packets, not the request packets.
I used the NTT [0] BGP looking glass (GIYF) to traceroute from
their Chicago router to your ISP's 178.191.255.254 [2] and got
no further than Level 3.
So over to Level 3's looking glass and a BGP check for your ISP's
178.191.0.0/16 shows no route.
So this is a problem for you to take up with your ISP. They need
to barter or pay for BGP peers to announce their ASN globally.
--Mike
[0]
I chose NTT at random. If NTT had a route to you I would
have investigated further to see why Tim's return packets
were non-routable.
[1]
# traceroute -p 80 -T trinitydesktop.org
traceroute to trinitydesktop.org (192.119.205.246), 30 hops max, 60 byte
packets
1 * * *
2 23.92.75.17 (23.92.75.17) 0.218 ms 0.203 ms 0.167 ms
3 63.141.218.141 (63.141.218.141) 0.145 ms 0.475 ms 0.467 ms
4 xe-1-2-0.cr3-sea2.ip4.gtt.net (89.149.181.213) 0.287 ms
xe-11-0-2.cr3-sea2.ip4.gtt.net (89.149.184.142) 0.218 ms
xe-1-2-0.cr3-sea2.ip4.gtt.net (89.149.181.213) 0.259 ms
5 as7018.ip4.gtt.net (216.221.156.158) 4.656 ms 4.650 ms 4.634 ms
6 cr84.st0wa.ip.att.net (12.122.158.162) 53.941 ms 53.932 ms 53.906 ms
7 * * *
8 cr2.cgcil.ip.att.net (12.122.2.117) 52.537 ms 52.533 ms 52.434 ms
9 cr2.sl9mo.ip.att.net (12.122.2.22) 52.841 ms 52.415 ms 52.381 ms
10 12.122.152.201 (12.122.152.201) 82.086 ms 154.078 ms 154.048 ms
11 * * *
12 * * *
13 * * *
14 edge.pearsoncomputing.net (192.119.205.244) 72.064 ms 78.015 ms 85.089
ms
15 trinitydesktop.org (192.119.205.246) 90.907 ms 70.206 ms 88.097 ms
[2]
Tracing the route to 178.191.255.254
1 *
Xe-9-1-edge2.nwr1.level3.net (4.68.111.69) 0 msec 0 msec
2 * * *
3-30 * * *
Many firewalls will drop UDP 80. Try adding the
-T flag.
It does not change anything. The domains are still unreachable.
Very sad!
8:56 p.m.
New subject: [SOLVED] Re: trinitydesktop.org and bugs.pearsoncomputing.net unreachable from time to time
Mike Bird wrote:
On Wed October 12 2016 10:24:17 deloptes wrote:
Thanks for confirming this. Looks like someone left a sh*T and cleaned up
later. The issue was just solved recently. Now it works again.
Indeed it looks like it was with the local provider, because from another
local provider I was able to reach it.
regards
Mike Bird wrote:
The server is reachable (on TCP 80 but not UDP 80) by me from
five different test locations. Two of these use the same
ultimate route as your traffic via 12.122.152.201 e.g. [1].
This suggests that the problem lies in the routing of the
response packets, not the request packets.
I used the NTT [0] BGP looking glass (GIYF) to traceroute from
their Chicago router to your ISP's 178.191.255.254 [2] and got
no further than Level 3.
So over to Level 3's looking glass and a BGP check for your ISP's
178.191.0.0/16 shows no route.
So this is a problem for you to take up with your ISP. They need
to barter or pay for BGP peers to announce their ASN globally.
--Mike
[0]
I chose NTT at random. If NTT had a route to you I would
have investigated further to see why Tim's return packets
were non-routable.
[1]
# traceroute -p 80 -T trinitydesktop.org
traceroute to trinitydesktop.org (192.119.205.246), 30 hops max, 60 byte
packets
1 * * *
2 23.92.75.17 (23.92.75.17) 0.218 ms 0.203 ms 0.167 ms
3 63.141.218.141 (63.141.218.141) 0.145 ms 0.475 ms 0.467 ms
4 xe-1-2-0.cr3-sea2.ip4.gtt.net (89.149.181.213) 0.287 ms
xe-11-0-2.cr3-sea2.ip4.gtt.net (89.149.184.142) 0.218 ms
xe-1-2-0.cr3-sea2.ip4.gtt.net (89.149.181.213) 0.259 ms
5 as7018.ip4.gtt.net (216.221.156.158) 4.656 ms 4.650 ms 4.634 ms
6 cr84.st0wa.ip.att.net (12.122.158.162) 53.941 ms 53.932 ms 53.906
ms
7 * * *
8 cr2.cgcil.ip.att.net (12.122.2.117) 52.537 ms 52.533 ms 52.434 ms
9 cr2.sl9mo.ip.att.net (12.122.2.22) 52.841 ms 52.415 ms 52.381 ms
10 12.122.152.201 (12.122.152.201) 82.086 ms 154.078 ms 154.048 ms
11 * * *
12 * * *
13 * * *
14 edge.pearsoncomputing.net (192.119.205.244) 72.064 ms 78.015 ms
85.089 ms
15 trinitydesktop.org (192.119.205.246) 90.907 ms 70.206 ms 88.097 ms
[2]
Tracing the route to 178.191.255.254
1 *
Xe-9-1-edge2.nwr1.level3.net (4.68.111.69) 0 msec 0 msec
2 * * *
3-30 * * * Many firewalls will drop UDP 80. Try adding the
-T flag.
It does not change anything. The domains are still unreachable.
Very sad!
2762
days inactive
2762
days old
4 comments
2 participants
participants (2)
-
deloptes -
Mike Bird