daisy-chain WRT54G behind another router?

Discussion in 'Cisco/Linksys Wireless Routers' started by DannoXYZ, Oct 26, 2006.

  1. DannoXYZ

    DannoXYZ Guest

    Hi, we've got some new attourneys in the office and I'd like to set them up on an isolated network, yet still share the internet-connection and printers. They brought with them a 4-port WRT54G and I'd like to install it into our existing 4-port D-link DI614+ which is providing the NAT gateway to the internet. Here's is the existing network:

    INTERNET -> modem (70.165.x.x) -> Dlink (192.168.0.x) -> 2 computers, printer, network-HD, 1 laptop on wireless.

    To hook up the WRT54G behind the Dlink, I've set it up with incoming WAN IP of and set it's LAN side to 192.168.1.x to keep them on separate subnet for security. I plugged the WRT54G into the 4th port of the Dlink and hooked their computers up to the LAN side and it worked! The double-NAT doesn't seem to be causing any issues as far as speed or internet/email access. The DNS issues presented in [url='Correct' way to put one router behind another?]this thread[/url] actually works in my favor because it prevents their computers on teh 192.168.1x network from browsing our computers on the 192.168.0.x side.

    However, here's the problem, trying to intentionally routing stuff between each side of the WRT54G.

    1. Due to all ports being used on the WRT54G, I have to install their copier/printer/fax machine on our Dlink, but it's got an IP of and all their software is expecting that IP for printing & scanning. How do I set the routing-table to have this printer on the WAN side of the WRT54G to be accessible by the computers on the LAN side. Would this IP even work hooked up to the Dlink's 192.168.0.x side?

    2. I'd also like to share our printer with IP of with their computers on the 192.168.1.x side. How do I set up the routing table for that?

    3. Similar issue with the network-HD with IP of, I'd like for them to be able to access it for backups

    4. finally, I'd prefer to turn off the Dlink's wireless and use the WRT54G instead for it's WAP+PSK encryption. Would it be possible to use IPs of 192.168.0x on the WRT54G to keep our laptops separate from their computers?

    I've tried switching the WRT54G from gateway to router mode and nothing worked at all, not even internet-access, so I put it back to gateway. The actual implementation is not set in stone, I'd just like to hook the existing hardware up in some fashion that has security and separate of the two sets of workgroups, and yet still share the internet-connection and printers. Any suggestions would be greatly appreciated, thanks. :)

    BTW - I've got subnet of on everything.
  2. rickyschrieber

    rickyschrieber LI Guru Member

    I believe that since you are using two separated subnets you need a master browser on one leg and a domain master browser the other to tie it together since it is not routed.
    Since the 1.xx network can't browse the 0.xx you can add a local entry to the 1.xx computers etc\drivers\hosts "printer" or give them the address of a server that will be the print spooler.
    I presume that DNS servers for 1.xx is your WRT54G so maybe you could tell it to use your 0.xx DNS server and bury the printer/spooler address there.
  3. ifican

    ifican Network Guru Member

    In a nutshell can you do what you are attempting to do with your current equipment, No. Now as far as sharing stuff on the 0.x network so users from the 1.x network can access should be no issue, just have then access the device via ip instead of name (Map drives, printers etc by ip). Your wireless clients will only work with ip's from the lan side range they are connected too.

    The easiest fix for your current situation minus the wireless is to buy a small inexpensive switch and plug it into the lan side of the 1.x network and then hand printers or whatever else still needs to be added to the 1.x network off the switch so the users of that network will have access. That will give the 1.x users access to their printers and still allow them to access anything that you give them permission to on the 0.x network via ip but not vice versa unless you specifically allow the incomming traffic to the 1.x router.
  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