If you issue a command line traceroute, what do you see? PingPlotter goes off of traceroute - so it should be showing you the same thing as command line. Let us know!
Thanks for replying.
tracert 8.8.8.8 (for example) shows the same anomaly -- it skips the first hop to the gateway.
-----------------------------------------------------
C:\Users\RDP1User>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 37 ms 30 ms 33 ms 172.26.96.161
3 49 ms 36 ms 38 ms 107.72.231.228
4 * * * Request timed out.
5 71 ms 36 ms 28 ms 12.83.179.49
6 29 ms 27 ms 35 ms 12.122.104.117
7 52 ms 36 ms 35 ms 12.255.10.162
8 * * * Request timed out.
9 34 ms 54 ms 30 ms 74.125.251.38
10 34 ms 36 ms 34 ms 108.177.3.235
11 45 ms 34 ms 33 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\Users\RDP1User>tracert 192.168.100.1
Tracing route to 192.168.100.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.100.1
------------------------------------------------------
And here's the route table of the PC on which I'm running PingPlotter:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.100.1 192.168.100.30 281
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.100.0 255.255.255.0 On-link 192.168.100.30 281
192.168.100.30 255.255.255.255 On-link 192.168.100.30 281
192.168.100.255 255.255.255.255 On-link 192.168.100.30 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.100.30 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.100.30 281
===========================================================================
As you can see, traffic has to pass through the gateway at 192.168.100.1.
So, not a problem with PingPlotter per se. But a puzzle discovered while using PingPlotter.
Anyhow, this seems to be a question that arises not infrequently, as
google traceroute skips gateway first hop
shows. Looks like it's to do with router configuration, and apparently the router not decrementing the ping packet TTL counter. So I guess I'll research it along that path.