said by gew1:I've not been able to hit Veetle.com for more than 3 weeks. From my location, (N.E, eastern MA) port 80 to veetle.com is simply unavailable.
And you wont be able to until Veetle decides to fix there firewalls so they stop them from blocking TCP port 80 from select IPs.
Additionally, you have to love when a "website/sysadmin" posts things like this. The fact is if veetle2/Peter had any clue how to diagnose issues he would know how to run a trace using a specific port and protocol and not ask for some other program to be used. Case in point:
Normal trace, default settings
traceroute to Veetle.com (77.67.109.221), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.294 ms 0.570 ms 0.566 ms
2 L100.BLTMMD-VFTTP-14.verizon-gni.net (72.81.130.1) 2.634 ms 2.716 ms 2.866 ms
3 130.81.185.154 (130.81.185.154) 3.651 ms 3.755 ms 3.755 ms
4 so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net (130.81.199.4) 6.076 ms ae1-0.PHIL-BB-RTR1.verizon-gni.net (130.81.209.238) 44.140 ms so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net (130.81.199.4) 5.930 ms
5 0.xe-3-0-2.XL4.IAD8.ALTER.NET (152.63.3.57) 8.309 ms 0.xe-6-1-1.XL3.IAD8.ALTER.NET (152.63.3.245) 8.511 ms 0.xe-3-0-2.XL4.IAD8.ALTER.NET (152.63.3.57) 8.497 ms
6 GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET (152.63.33.17) 12.071 ms GigabitEthernet6-0-0.GW8.IAD8.ALTER.NET (152.63.33.13) 11.719 ms 10.967 ms
7 tinet-gw.customer.alter.net (152.179.50.30) 11.825 ms 11.450 ms 11.309 ms
8 xe-3-0-0.pao10.ip4.tinet.net (141.136.111.193) 79.820 ms xe-1-3-0.pao10.ip4.tinet.net (141.136.109.98) 80.916 ms xe-3-0-0.pao10.ip4.tinet.net (141.136.111.193) 78.348 ms
9 77.67.109.221 (77.67.109.221) 77.410 ms 78.168 ms 76.325 ms
Trace to port TCP/80 (-T --tcp Use TCP SYN for tracerouting (default port is 80))
fw1@core:~$ sudo traceroute -T Veetle.com
traceroute to Veetle.com (77.67.109.220), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.180 ms 0.174 ms 0.191 ms
2 L100.BLTMMD-VFTTP-14.verizon-gni.net (72.81.130.1) 1.584 ms 1.695 ms 1.875 ms
3 G0-5-2-4.BLTMMD-LCR-21.verizon-gni.net (130.81.49.0) 4.515 ms 4.643 ms 4.636 ms
4 so-1-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.199.2) 5.080 ms ae4-0.RES-BB-RTR1.verizon-gni.net (130.81.209.230) 6.925 ms so-1-1-0-0.RES-BB-RTR1.verizon-gni.net (130.81.199.2) 6.902 ms
5 0.so-6-0-2.XL3.IAD8.ALTER.NET (152.63.36.233) 8.202 ms 0.xe-4-1-0.XL4.IAD8.ALTER.NET (152.63.2.253) 9.545 ms 0.so-6-0-2.XL3.IAD8.ALTER.NET (152.63.36.233) 8.622 ms
6 GigabitEthernet6-0-0.GW8.IAD8.ALTER.NET (152.63.33.13) 9.673 ms GigabitEthernet4-0-0.GW8.IAD8.ALTER.NET (152.63.33.93) 7.486 ms GigabitEthernet6-0-0.GW8.IAD8.ALTER.NET (152.63.33.13) 9.332 ms
7 tinet-gw.customer.alter.net (152.179.50.30) 10.207 ms 8.870 ms 8.844 ms
8 xe-3-0-0.pao10.ip4.tinet.net (141.136.111.193) 77.289 ms 78.200 ms xe-5-0-0.pao10.ip4.tinet.net (141.136.111.189) 78.964 ms
9 * * *
10 * * *
11 * * *
12 * * *
Clearly traffic to port TCP/80 is being blocked (Most likely more ports as well) at the edge of there network either by there server or there ISP, why they are blocking it i don't know/care since before this thread i have never visited it and probably wont again in the future.