Can't ping devices on client-mode router

Discussion in 'Tomato Firmware' started by tinyboss, Sep 27, 2009.

  1. tinyboss

    tinyboss Addicted to LI Member

    [SOLVED] Can't ping devices on client-mode router

    I'm using Tomato on both my home routers. My main router is connected to the modem and provides internet to the whole network, but it's in the kitchen because there's no phone outlet in the living room.

    My client router is in the living room, running in wireless client mode, with my XBox, network storage, and network printer wired to it. The problem is that anything connected wirelessly to my main router is unable to see the devices that are wired to the client router.

    Is this a limitation of the client setup, or do I have something configured wrong? The tutorial I read said that devices on the client could see things on the main router, but didn't say anything about the other direction.

    If this won't work, then I'll have to move my printer and NAS back into the kitchen. Ugh. Any help is appreciated!
  2. anik

    anik Addicted to LI Member

    Since no one else has replied yet, I'll just throw something out that may or may not be helpful - bear in mind that in this case you're getting the blind leading the blind, so to speak, because I'm not an expert in this stuff.

    What too often happens in a situation like this is that each router is assigning its own IP addresses. Let's say you main router is assigning addresses in the 192.168.0.x range. Now you add a second router and tell it to assign addresses in the 192.168.1.x range. The computers connected to the second router can see all the devices on both networks but the ones connected to the first router can only see devices connected to its segment. Does that pretty much describe your situation?

    If so, part of the issue would be (using the above example) that when you try to go to a 192.168.1.x address from the top level network, it doesn't realize that address is on its network, and sends the request out to the Internet instead of looking for that address on its own network!

    So what should be happening is that the second router should not be assigning IP addresses at all - it should be operating in "bridge mode" (I think it is called) where the top-level router assigns all the addresses for all devices no matter which router they are connected to. All devices would get addresses in the 192.168.0.x range (or whatever you're using) and the top-level router would handle routing for all of them.

    But if for some reason you can't do that, one quick fix that sometimes works is to expand the netmask on the primary router so that it at least knows that it should be looking for addresses on the other segment in its own network. For example if you have addresses in the 192.168.x.x range on both routers, then the netmask on the top-level router (and all devices connected to that network that don't pull information from the router using DHCP) should be set to (instead of There may be something else you'd need to do (as I say, I'm not a networking expert by any means) but at least by changing the netmask you end the problem of requests for the other network segment being sent out your gateway to the Internet.

    Now if someone else responds and says I'm wrong about something I've said here, listen to them because they probably know more than I do. But the above is my limited understanding about why you might be having the problem.
  3. tinyboss

    tinyboss Addicted to LI Member

    Thank you, anik, for the reply!

    That is indeed my situation: my top-level-connected devices cannot see my client-connected devices. I did try expanding the netmask without any result, but at this point there are about a dozen settings that I suspect are relevant, so maybe that's a component of the solution I'm looking for.

    To everyone: I've been experimenting with setting both routers to different IP's in the same 192.168.2.* subnet. Ideally I'd like all my devices to think they're on the same network, as if I didn't even have a wireless-client-mode router involved. Is this even possible, or should I stop trying this angle?

    One thing I've tried twice (with the same result) is setting the client to use a static IP of, and the main router to When I try this, something goes really wrong with the client and afterward I can't even administer it via cable with the main router powered off--I have to reset to defaults.
  4. tinyboss

    tinyboss Addicted to LI Member

    The solution was to use "Wireless Ethernet Bridge" mode instead of "Wireless Client". There was some kind of problem where if I reset the router's settings, then put it in bridge mode, it wouldn't associate to the main router. I *think* this was solved by putting it into client mode, getting it to connect properly, *then* changing to bridge mode. But that was during the fourth hour of twiddling settings, so I'm not 100% sure what the key was. At any rate, it's working now, in bridge mode.
  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