Mike Bird wrote: > On Wed October 12 2016 10:24:17 deloptes wrote: >> Mike Bird wrote: >> > Many firewalls will drop UDP 80. Try adding the -T flag. >> >> It does not change anything. The domains are still unreachable. >> >> Very sad! > > 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 * * * 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 --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
