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

WRT160N v3 static routes to USR 8054

Discussion in 'Networking Issues' started by dalexop, May 3, 2011.

  1. dalexop

    dalexop Networkin' Nut Member

    Hi folks,
    here's a bizarre question.

    I have static routes setup between these two routers.

    The US Robotics WAN port is connected to LAN Port 2 on the WRT 160N
    The WRT 160 N is then connected to the internet via its LAN port.

    I have a static route pointing the USR to the WRT over the WAN port.
    I have another static route from the WRT pointing back to the USR router via Eport 2.

    I can ping hosts from the USR to the WRT.
    I cannot ping hosts from the WRT over to those on the USR.

    The Route Tables look good, entries are complete.

    Are there service codes or diagnstics I can look at to see what the WRT Router is trying to do ?

    Thanks
    Derek
     
  2. Toxic

    Toxic Administrator Staff Member

    Is there a firewall on your WAN port of the USR router?
     
  3. dalexop

    dalexop Networkin' Nut Member

    Hey Toxic !

    Yes sir, but I entered a rule to allow all traffic.

    I think that the Ping from USR LAN through WAN to WRT LAN would not work if the F/W was enabled.
    The return ping would be filtered, since it's traversing IP subnets.

    If I run TraceRT, the USR side understands that there is a local interface to hit prior to the remote subnet.

    TraceRT on the WRT never see's it's own LAN interface.

    I really wish there was a diagnostics screen showing packet status.
    The Routing Table looks OK funny enough.
     
  4. dalexop

    dalexop Networkin' Nut Member

    Update:
    I've worked for a while trying to understand whether packets were being dropped, or they were not routerd properly.
    the USRobotics box is an old router and has its share of challenges.

    I ended up going with another Linksys 160N from eBay.
    This should clear up my issues pretty quickly.

    I'll update this thread once I fix this for good !
     

Share This Page