1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WRT54GS v1.0 Traceroute Issues

Discussion in 'Cisco/Linksys Wireless Routers' started by Maxx, Feb 11, 2005.

  1. Maxx

    Maxx Network Guru Member

    I am not sure if it is the router causing this "problem" (and if I should even consider this as a problem) or if its the OS (XP SP2+), TCP/IP settings (nothing radical), router settings (nothing radical, US-spec Firmware Version: v3.37.6) etc. - all I know is that the speedguide networktools traceroute from that site back to my cable modem always "worked" and traced each hop when my WiFi network was based on the 802.11b Linksys products (NICs, Router)... apart from installing the WRT54GS v1.0 and complementary 54g NICs - nothing has changed in my configuration and/or setup. Currently the traceroute times-out at the hop where it should register my cable modem's IP address. Here are the results:

    Ping Results:

    PING 66.xxx.xxx.xx (66.xxx.xxx.xx) 56(84) bytes of data.
    64 bytes from 66.xxx.xxx.xx: icmp_seq=1 ttl=55 time=16.1 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=2 ttl=55 time=13.5 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=3 ttl=55 time=12.4 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=4 ttl=55 time=16.9 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=5 ttl=55 time=13.9 ms

    --- 66.xxx.xxx.xx ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4050ms
    rtt min/avg/max/mdev = 12.410/14.591/16.910/1.674 ms

    Traceroute Results:

    1 63-217-30-94.sdsl.cais.net (63.217.30.94) 8.754 ms 0.254 ms 0.227 ms
    2 ge6-2.cr02.ash01.pccwbtn.net (63.218.44.82) 0.310 ms 0.220 ms 0.224 ms
    3 pop2-ash-P12-0.atdn.net (66.185.141.193) 0.308 ms 0.285 ms 0.379 ms
    4 bb2-ash-P1-0.atdn.net (66.185.139.210) 0.635 ms 0.907 ms 0.531 ms
    5 bb1-nye-P3-0.atdn.net (66.185.152.86) 6.279 ms 6.451 ms 6.540 ms
    6 pop2-nye-P0-0.atdn.net (66.185.151.65) 5.853 ms 6.218 ms 6.203 ms
    7 RR-Queens.atdn.net (66.185.141.38 ) 6.113 ms 6.198 ms 6.071 ms
    8 pos1-0-nycmnyc-rtr2.nyc.rr.com (24.29.101.250) 6.225 ms 6.276 ms 6.191 ms
    9 pos1-0-nycmnyc-ubr8.nyc.rr.com (24.29.97.90) 6.615 ms 6.610 ms 6.562 ms
    10 pos2-0-nycmnyc-ubr7.nyc.rr.com (24.29.97.85) 7.119 ms 53.476 ms 6.491 ms
    11 * * *
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    .............
    30 * * *

    Previously (with a 802.11b Router) these used to look like this (and still do with the cable modem connected directly to a wired NIC):

    Ping Results:

    PING 66.xxx.xxx.xx (66.xxx.xxx.xx) 56(84) bytes of data.
    64 bytes from 66.xxx.xxx.xx: icmp_seq=1 ttl=119 time=12.1 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=2 ttl=119 time=12.9 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=3 ttl=119 time=13.3 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=4 ttl=119 time=12.8 ms
    64 bytes from 66.xxx.xxx.xx: icmp_seq=5 ttl=119 time=14.4 ms

    --- 66.xxx.xxx.xx ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4034ms
    rtt min/avg/max/mdev = 12.189/13.153/14.430/0.738 ms

    Traceroute Results:

    1 63-217-30-94.sdsl.cais.net (63.217.30.94) 0.292 ms 0.251 ms 0.262 ms
    2 ge6-2.cr02.ash01.pccwbtn.net (63.218.44.82) 0.310 ms 0.277 ms 0.201 ms
    3 pop2-ash-P12-0.atdn.net (66.185.141.193) 0.597 ms 0.354 ms 0.355 ms
    4 bb2-ash-P1-0.atdn.net (66.185.139.210) 0.466 ms 0.480 ms 0.674 ms
    5 bb1-nye-P3-0.atdn.net (66.185.152.86) 5.810 ms 5.780 ms 5.872 ms
    6 pop2-nye-P0-0.atdn.net (66.185.151.65) 230.298 ms 6.527 ms 5.866 ms
    7 RR-Queens.atdn.net (66.185.141.38 ) 6.079 ms 6.077 ms 6.044 ms
    8 pos1-0-nycmnyc-rtr2.nyc.rr.com (24.29.101.250) 6.319 ms 6.331 ms 6.263 ms
    9 pos1-0-nycmnyc-ubr8.nyc.rr.com (24.29.97.90) 6.715 ms 6.665 ms 7.176 ms
    10 pos2-0-nycmnyc-ubr7.nyc.rr.com (24.29.97.85) 6.815 ms 6.434 ms 6.707 ms
    11 66-xxx-xxx-xx.nyc.rr.com (66.xxx.xxx.xx) 12.356 ms 13.605 ms 12.273 ms

    Any comments? Ideas? Solutions?

    PS - UPDATE: If I use the router's built-in traceroute diagnostic feature I now CAN NOT complete a trace from the router back to speedguide.net or any other IP or domain name. The same is true for the built-in PING diagonstic feature. Strange as both used to work just a few days before. Anyhow - here is a trace using Ping Plotter.


    Target Name: 63-217-30-94.sdsl.cais.net
    IP: 63.217.30.94
    Date/Time: 2/10/2005 10:30:33 PM

    1 2 ms 1 ms 2 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms [192.168.1.1]
    2 11 ms 16 ms 8 ms 12 ms 8 ms 15 ms 7 ms 25 ms 13 ms [10.34.192.1]
    3 11 ms 12 ms 6 ms 8 ms 7 ms 11 ms 12 ms 9 ms 11 ms pos0-3-nycmnyc-rtr1.nyc.rr.com [24.29.97.81]
    4 7 ms 7 ms 8 ms 9 ms 6 ms 11 ms 22 ms 8 ms 16 ms pos0-0-nycmnyrdc-rtr1.nyc.rr.com [24.29.97.17]
    5 16 ms 11 ms 11 ms 18 ms 7 ms 22 ms 15 ms 18 ms 12 ms pop2-nye-P10-0.atdn.net [66.185.141.33]
    6 8 ms 19 ms 11 ms 9 ms 17 ms 11 ms 10 ms 12 ms 12 ms bb1-nye-P1-0.atdn.net [66.185.151.64]
    7 26 ms 14 ms 15 ms 14 ms 17 ms 17 ms 13 ms 13 ms 13 ms bb2-ash-P10-0.atdn.net [66.185.152.87]
    8 25 ms 24 ms 13 ms 23 ms 15 ms 13 ms 18 ms 17 ms 14 ms pop2-ash-P1-0.atdn.net [66.185.139.211]
    9 16 ms 13 ms 14 ms 20 ms 15 ms 13 ms 15 ms 14 ms 16 ms BeyondTheNetwork.atdn.net [66.185.141.194]
    10 12 ms 24 ms 14 ms 30 ms 14 ms 21 ms 27 ms 13 ms 15 ms 63-217-30-94.sdsl.cais.net [63.217.30.94]
     
  2. Maxx

    Maxx Network Guru Member

    Thanks for all your help - LI.ORG is the place to be.
     

Share This Page