Thread:Dragonjet/@comment-26372522-20150920130055/@comment-26091666-20150920154840

Sadly it appears that PingPlotter is using the traditional method of testing to see if the host is up. Technically speaking it is using ICMP packets which agrees with what Dragonjet spoke about normal pings. Is there a way for you to be able to configure the program so that it could traceroute via TCP instead of ICMP?

I found a site where you can do traceroute using an alternative method (TCP) as opposed to ICMP and in that regards it is quite similar to the tool I am using on my own computer. The results indicate that the host (125.6.189.135) is definitely up as it is also revealed on my end.

I ran a few traceroutes on my end and here are the results. In short I think it might be a host or two on your connection, namely node 5 and 6 are showing up on my end as either closed or down. Of course I have removed personal information from my outputs: $ lft -e 125.6.189.215 Tracing .***********.....**.........*!.!...........T TTL LFT trace to 125.6.189.215:80/tcp ** [firewall] the next gateway may statefully inspect packets 1 gateway (192.168.1.254) 0.5/0.6ms 2 xxx.xxx.xxx.xxx 50.2/57.6ms 3 xxx.xxx.xxx.xxx 15.6/41.2ms 4 xxx.xxx.xxx.xxx 36.3/53.9ms 5 xxx.xxx.xxx.xxx 31.8/47.8ms 6 xxx.xxx.xxx.xxx 142.3/142.1ms 7 180.87.112.150 234.4/233.1ms 8 tky001bb08.IIJ.Net (58.138.99.25) 259.5/241.4ms 9 tky001bf00.IIJ.Net (58.138.82.129) 249.5/241.0ms 10 tky009bb11.IIJ.Net (58.138.80.194) 268.9/238.8ms 11 tky009ip58.IIJ.Net (58.138.112.226) 237.1/238.8ms 12 210.138.133.218 267.1/259.9ms 13 203.174.66.150 279.8/261.1ms 14 [target open] 125.6.189.215:80 259.0ms Here is where I ran lft on my own game host (Paramushir).

$ lft -e 125.6.189.135 Tracing .************.....**........*!.!............T TTL LFT trace to 125.6.189.135:80/tcp ** [firewall] the next gateway may statefully inspect packets 1 gateway (192.168.1.254) 0.5/0.7ms 2 xxx.xxx.xxx.xxx 35.3/16.8ms 3 xxx.xxx.xxx.xxx 16.9/83.7ms 4 xxx.xxx.xxx.xxx 30.1/67.2ms 5 xxx.xxx.xxx.xxx 32.3/50.9ms 6 xxx.xxx.xxx.xxx 142.1/142.5ms 7 180.87.112.150 234.4/233.0ms 8 tky001bb08.IIJ.Net (58.138.99.25) 249.0/241.7ms 9 tky001bf01.IIJ.Net (58.138.82.133) 285.6/242.3ms 10 tky009bb11.IIJ.Net (58.138.80.198) 235.0/240.0ms 11 tky009ip58.IIJ.Net (58.138.112.234) 228.8/228.9ms 12 210.138.133.218 259.1/268.7ms 13 203.174.66.150 260.6/263.1ms 14 [target open] 125.6.189.135:80 260.8ms I ran my tool against your game host (Brunei).

$ lft -e 125.6.189.215 Tracing .************....**.........*!.!............T TTL LFT trace to 125.6.189.215:80/tcp ** [firewall] the next gateway may statefully inspect packets 1 gateway (192.168.1.254) 0.5/0.6ms 2 xxx.xxx.xxx.xxx 15.8/16.0ms 3 xxx.xxx.xxx.xxx 21.9/28.9ms 4 xxx.xxx.xxx.xxx 29.0/44.5ms 5 xxx.xxx.xxx.xxx 31.9/30.4ms 6 xxx.xxx.xxx.xxx 159.4/146.0ms 7 180.87.112.150 252.4/234.3ms 8 tky001bb08.IIJ.Net (58.138.99.25) 241.2/240.9ms 9 tky001bf00.IIJ.Net (58.138.82.129) 240.9/247.2ms 10 tky009bb11.IIJ.Net (58.138.80.194) 251.6/238.0ms 11 tky009ip58.IIJ.Net (58.138.112.226) 238.1/259.4ms 12 210.138.133.218 259.1/260.6ms 13 203.174.66.150 262.5/260.9ms 14 [target open] 125.6.189.215:80 267.2ms I ran it again on my end to see double check, all is well.

$ lft -e 203.192.137.13 Tracing .************.....***.*....*.........T TTL LFT trace to TM.asianetcom.net (203.192.137.13):80/tcp ** [firewall] the next gateway may statefully inspect packets 1 gateway (192.168.1.254) 0.5/0.6ms 2 xxx.xxx.xxx.xxx 16.3/21.2ms 3 xxx.xxx.xxx.xxx 48.0/16.9ms 4 xxx.xxx.xxx.xxx 35.3/38.9ms 5 xxx.xxx.xxx.xxx 32.5/33.3ms 6 xxx.xxx.xxx.xxx 29.2/30.4ms 7 gi10-2.gw1.syd5.asianetcom.net (202.147.14.213) 29.6/30.8ms 8 gi4-1-3.gw5.hkg3.asianetcom.net (203.192.174.223) 260.8/288.9ms 9 [target closed] TM.asianetcom.net (203.192.137.13):80 253.4/266.9ms I set my target on your 5th node (TM.asianetcom.net) it appears to either be filtered or actually down probably.

$ lft -e 202.147.0.55 Tracing .************.....*****.***** TTL LFT trace to ge3-1-0-0.gw3.nrt4.asianetcom.net (202.147.0.55):80/tcp ** [firewall] the next gateway may statefully inspect packets 1 gateway (192.168.1.254) 0.6ms 2 xxx.xxx.xxx.xxx 16.7ms 3 xxx.xxx.xxx.xxx 24.0ms 4 xxx.xxx.xxx.xxx 77.2ms 5 xxx.xxx.xxx.xxx 61.0ms 6 xxx.xxx.xxx.xxx  42.7ms 7 gi10-2.gw1.syd5.asianetcom.net (202.147.14.213) 46.2ms ** [80/tcp no reply from target]  Try advanced options (use -VV to see packets). On this last output it shows that the 6th node from your screenshot is either filtering it or is down.

The results are preliminary and it is best at that. Unless node 5, 6 and 7 of your screenshot are actually up on your end then that particular network or a segment of it is down.