I don't see a problem here ? According to RFC 1918 the Net 10 and Net 172.16/12 and 192.168/16 addresses are for use privately or internally such as when : " - Interfaces of routers on an internal network usually do not need to be directly accessible from outside the enterprise." These addresses are however not advertised to the outside world and should thus cause no problem here. We are simply seeing those net 10 addresses as a source address for those packets returned by the traceroute, but that address should not be reacheable or advertised from outside the internal network. See http://www.cis.ohio-state.edu/htbin/rfc/rfc1918.html for more details. Thanks Pat @Home Network Operations Once upon a time, Marc Hurst arranged the electrons in @Home's private scaleable, ATM, OC3 BackBone to write:
Subject: Someones being naughty again... (Mar 13, 6:56pm) Here is a traceoute from BBN Planet to my machine... (sorry D, couldn't resist...:)
traceroute to 24.112.43.xx (24.112.43.xx), 30 hops max, 40 byte packets 1 netgwb (205.227.188.1) 196 ms 611 ms 9 ms 2 oakland-cr2.bbnplanet.net (4.0.68.77) 20 ms 15 ms 19 ms 3 oakland-br2.bbnplanet.net (4.0.16.17) 16 ms 15 ms 22 ms 4 sanjose1-br1.bbnplanet.net (4.0.1.74) 25 ms 16 ms 15 ms 5 bb.mae-w.home.net (198.32.136.70) 19 ms 17 ms 21 ms 6 172.16.2.174 (172.16.2.174) 110 ms 108 ms 107 ms 7 r3-fe0-0-100bt.rdc1.on.wave.home.net (24.2.9.4) 121 ms 108 ms 112 ms 8 10.0.184.34 (10.0.184.34) 153 ms 109 ms 106 ms 9 pc-30xxx.on.rogers.wave.ca (24.112.43.xx) 110 ms 111 ms 110 ms
Nice 10.x.x.x. End of included message written by Marc Hurst on Mar 13, 6:56pm,