Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

WAN Tracecert (Traceroute) log 192.168.x.x -> 10.x.x.x

I live in Washington D.C area.  My house uses verizon service(DSL) for internet (Westell 6100 modem + route).  Also, my office uses Cox DSL line (Arina modem + Llinksys router)

When I tracert to "google" it goes 10.x.x.x which is not my router, and it takes almost 7ms to reach there. (Obviously not my device). What is this private range? I can see this from Cox and Verizon DSL line. The below is the output of one of tracert from office.

Does this mean that verizon or cox deal my packet through their internal (priviate) router?

FYI, I use my westell box for bridge mode, and I put netgear router (so basically modem doesn't do anything)

also, our office does have only modem provided by cox, and we use Linksys RV016 router for gateway. 

Do you have any idea?

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users> tracert www.google.com

Tracing route to www.l.google.com [173.194.34.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     7 ms     7 ms  10.1.104.1
  3     8 ms     7 ms     7 ms  ip72-219-223-213.dc.dc.cox.net [72.219.223.213]

  4     8 ms     9 ms     9 ms  mrfddsrj02gex070002.rd.dc.cox.net [68.100.0.145]

  5    15 ms    15 ms    15 ms  nyrkbprj02-ae2.0.rd.ny.cox.net [68.1.2.241]
  6    70 ms   109 ms    15 ms  72.14.238.232
  7    18 ms    17 ms    23 ms  216.239.48.44
  8    16 ms    15 ms    27 ms  lga15s15-in-f104.1e100.net [173.194.34.104]

Trace complete.

C:\Users

3 REPLIES

Re: WAN Tracecert (Traceroute) log 192.168.x.x -> 10.x.x.x

Hi,

It could be like cox has natted some private IP to public IP and this 10.1.104.1

could be one of them. I think it is better answered by provider. You have right to put query to

your provider

Regards

Mahesh

New Member

Re: WAN Tracecert (Traceroute) log 192.168.x.x -> 10.x.x.x

totally aggreed with Mahesh.. its very normal these days that ISP do 2nd time nat first time on your local DSL modem.. second time on ISP router.. so your 192 is sending to ISP.. check the gateway of your DSL router and if possible trace from your DSL.

New Member

Re: WAN Tracecert (Traceroute) log 192.168.x.x -> 10.x.x.x

Thanks for your reply.

I tried already couple of times to call ISP (verizon, cox) not only for my dsl line, bur also for my customers (I am working for remote desktop technician). but, tier 1,2 supporter, they don't know either. Also, they asked me to pay for tier 1 level support for 1 year with certain amount $. So, there was no further progress from there. It has been almost 3 years i exprienced this symptom.

The weired thing is "port forwarding". Most of time, when I open the port from router, it is open. However, sometimes, even if I open the port, port is closed no matter I put DMZ, still close. Whenever I have this issue, I call ISP to check, after that, port is open. So i guess, 2nd ISP router can block my in / out going packet somehow.

807
Views
0
Helpful
3
Replies