Troubleshooting transparent AP setup

Discussion in 'Tomato Firmware' started by ntucker, Dec 7, 2011.

  1. ntucker

    ntucker Networkin' Nut Member

    Hi all,
    I'm trying to use a tomato box (wrt54gs 2.1) as a transparent AP to create a wireless network that effectively extends the range of my main network. Main network is an 802.11n cisco device running default firmware, and I have no desire to mess with that. In fact, I don't even particularly care if the "extended" wireless network uses the same SSID as the main one. The important thing is that I want it to all be on the same subnet and have no NAT in between.

    So what I've done is set up the tomato box with a static IP, DHCP server disabled, with one of its LAN ports wired to the main LAN. Its WAN port is not hooked to anything. This works ... sort of. When I connect a PC to the tomato's wireless network, I sometimes get a proper DHCP response, and sometimes I don't. When I attempt to hook my android phone to it, it never gets a DHCP response.

    I'm at a bit of a loss as to how to troubleshoot this. It seems as though all the settings are correct, but obviously I've overlooked something. Any ideas?
  2. Toastman

    Toastman Super Moderator Staff Member Member

    You are trying to run it as a normal AP? Then connect a LAN port to a LAN port on the Cisco. Set WAN to disabled. Set an IP on the Tomato machine on the same subnet as the Cisco. Set mode as AP. Set DHCP to OFF. Set the default gateway as the Cisco's IP. Set the DNS to the Cisco's IP. Set wireless to use your preferred encryption (start with none to be sure it works first). That should work now.
  3. ntucker

    ntucker Networkin' Nut Member

    Yep, that's it exactly. If you were to try that and you didn't get any DHCP response, what would you check next?
  4. Toastman

    Toastman Super Moderator Staff Member Member

    Still using your PC's fixed IP:

    1) Ping the cisco and see if it always replies
    2) Ping, say, google's IP address from the PC and see if it's actually routed.
    3) Set PC's DNS to google's IP, and see if it now gets a DNS response.

    I expect you did all that already. Next .... mmm .... pray?
  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