traceroute to microsoft.com (13.107.213.41), 11 hops max, 46 byte packets
 1  NC8Q-KETTERING-MVHS.local.mesh (10.131.89.57)  2.807 ms
 2  dtdlink.NC8Q-HAP-AC3.local.mesh (10.207.77.99)  2.742 ms
 3  mid1.KQ4JAV-952Ui-102 (172.31.87.197)  29.632 ms
 4  mid12.KN9U-VA-Tunnel (172.31.20.48)  71.281 ms
 5  172.31.20.51 (172.31.20.51)  116.780 ms
 6  192.168.1.104 (192.168.1.104)  164.739 ms
 7  *
 8  100.64.0.1 (100.64.0.1)  95.625 ms
 9  172.16.250.16 (172.16.250.16)  119.151 ms
10  undefined.hostname.localhost (206.224.68.26)  391.593 ms
11  74.245.144.67 (74.245.144.67)  137.349 ms
root@NC8Q-MVHS-Kettering:~#

The above has been resolved with Matthew KN9U.

Now I am working on Chip n3fud:

root@NC8Q-MVHS-Kettering:~# traceroute -q 1 -m 9 microsoft.com
traceroute to microsoft.com (13.107.213.41), 9 hops max, 46 byte packets
 1  NC8Q-KETTERING-MVHS.local.mesh (10.131.89.57)  2.852 ms
 2  dtdlink.NC8Q-HAP-AC3.local.mesh (10.207.77.99)  6.006 ms
 3  mid1.KQ4JAV-952Ui-102 (172.31.87.197)  29.283 ms
 4  mid2.N3FUD-NCPA (172.31.38.98)  41.079 ms
 5  192.168.1.1 (192.168.1.1)  46.882 ms
 6  lo0-100.HRBGPA-VFTTP-311.verizon-gni.net (173.67.157.1)  44.913 ms
 7  100.41.24.84 (100.41.24.84)  44.193 ms
 8  *
 9  *
root@NC8Q-MVHS-Kettering:~#

73, Chuck