Two tomato routers, passing IP of source to other router

Discussion in 'Tomato Firmware' started by ctaranto, Mar 22, 2010.

  1. ctaranto

    ctaranto Addicted to LI Member

    I have a pair of WRT54GLs, both running Tomato 1.27 (SpeedMod). I'll name them R1 and R2.

    Comcast HSI/Motorols SB6120) -> R1 -> R2

    R1's WAN is DHCP from Comcast
    R1's LAN is

    R2's WAN is
    R2's LAN is

    On R1, I have the wireless disabled, a PAP2T VoIP adapter connected, and QoS enabled.

    On R2, I have the wireless enabled with a handful of wireless laptops, a switch that connects my TV, DirecTV DVR, Printer, etc. They all have a 172.x address.

    For QoS on R1, all traffic from R2 shows up as, which is understandable.

    My desire is see the actual IPs of the devices connected to R2 on R1 so I can better control QoS on traffic from R2 devices.

    Is there a way to "pass" the 172 addresses from R2 to R1? Or do I have to make R2 a "switch" instead of a "gateway" (making all IPs 192)?

    Any advice is appreciated.

  2. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    I would think that better than either of those two options would be to make it just a router (as opposed to gateway). That way, you could keep your separate subnet but not have a NAT.

    You'll need to set R2 to router mode (Advanced->Routing) and add a static route on R1 (Advanced->Routing, destination=, gateway=, mask=, interface=LAN).
  3. ctaranto

    ctaranto Addicted to LI Member

    That seems simple enough! I'll have to try this when I get home tonight - I'm not brave enough to do this over my work-to-home ssh connection.


  4. ctaranto

    ctaranto Addicted to LI Member

    I did this, but it didn't seem to make any difference. When I look in QoS on R1, I still see just for all activity from that router. I have started up a NX remote desktop session to my linux desktop at home (which is routed through R2), and I should see some activity on the "outbound" side of QoS on R1. It's all

    Also, with the above setting/static route, I could connect to the Linux desktop remotely via ssh, but the server itself couldn't go outwards to the internet (pinging didn't work, web didn't work).

    Any other ideas?


  5. ctaranto

    ctaranto Addicted to LI Member

    I misread what you said (I did both the static route and router setting on R2). I fixed it and looking at QoS now. Internet connectivity is restored.
  6. ctaranto

    ctaranto Addicted to LI Member

    Works great! FTP'd from a address (wireless connected to R2), and it showed up in QoS on R1!

    Thanks again,

  7. ctaranto

    ctaranto Addicted to LI Member

    Since I'm talking to myself in this thread ( :) ), I've noticed a small issue.

    I have an ssh server running on both R1 and R2. Both have been set up to run on port "x" for remote connections. I set up a Port Forward on R1, using external address "x+1" to forward to "x" on R2. It worked fine before changing R2 to "Router" and the static route in R1.

    Do the changes made effect the remote ssh connectivity to R2? If so, is there a way to resolve it?


  8. ctaranto

    ctaranto Addicted to LI Member

    Talking to myself again.

    I figured out what needed to change.

    When R2 is set up as Gateway, I needed to port forward (on R1) to the "Remote SSH port" (of R2). When R2 is set up as Router, I need to port forward (on R1) to the "local ssh port" (of R2). So I port forward to 22 on R2, changed the forward IP address from the WAN address to the LAN address (of R2), and now it works.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice