View Single Post
Old 15-01-2010, 23:52   #21
Ignitionnet
Inactive
 
Join Date: Jun 2008
Location: Leeds, West Yorkshire
Age: 47
Posts: 13,995
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Re: Painfully slow connection; can't get VM to help

Quote:
Originally Posted by Sephiroth View Post
Just to pick up on the 10.xx hop. The packet loss there is not reckonable into any problem you have. That address is the privately assigned IP address of the CMTS - the "you" side if you like. Your router or firewall could/would reject return pings. So that hop can be ignored.
Packet loss to the 10.x hop is most certainly worth considering - on all CMTS apart from the BSR whose first hop is a public address that is the CMTS.

Seph - a traceroute is simply a ping repeated with incrementing TTL until destination reached. The Cisco kit answers from the 10.x address which the cable modems talk to so that is what is seen. Either way it's the first hop after the HFC network and should be considered within diagnostics.

The cable modem does not show on any traceroute, it bridges all packets apart from those directed to its' management address so doesn't decrement TTL and doesn't appear in traceroutes. One can ping the cable modem's 10.x address if you happen to know it, it will happily respond, but it's a pointless exercise.
Ignitionnet is offline   Reply With Quote