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

WRT54G as an Access Point only?

Discussion in 'Cisco/Linksys Wireless Routers' started by dirtroad, Oct 13, 2005.

  1. dirtroad

    dirtroad Network Guru Member

    I'm trying to do something very simple (in theory) with a WRT54G that is not working. Hoping someone can help before I give up on it and do something different!

    Here is a simplified illustration of my network topology:

    Right now, this equipment is all in the same room. If I can make it work, it will eventually be deployed outside to deliver internet from my office to my parent's home 5 miles away.

    For those of you not familiar, the Airbridge in my illustration is a Smartbridges Airbridge. Essentially, it's like a 1 port WRT54G in client bridge mode. It bridges wifi to ethernet.

    In this case, I have the airbridge associated with the WRT54G and ethernet connected to the switch when in turn has internet access from the Dlink router. I have confirmed that the Airbridge is working correctly.

    What I need to do is have all the peers connected to the WRT54G get internet access from the Dlink router. This makes the WRT54G a simple access point. The problem is, it doesn't work.

    I have limited connectivity, in that PC#2 can ping and be pinged by PC#1. In fact, PC#2 can even log into the web interface for the Dlink router, and it's geting DHCP from it. But no outside traffic outside my lan works/no internet.

    Why isn't this working? I'm not even using the WRT54G as a router, just an AP... This should be easy.
  2. reber

    reber Network Guru Member

    Is your gateway set properly?

    And which firmware are you using? I've had really good experience with DD-WRT v22r2 operating a wireless client, but you intend for the wrt to initiate the bridge (as you've explained above).

    Should work regardless of the firmware. However, here's the link to DD-WRT.

    DD-WRT v22r2 firmware

    I'll tell you more about my specific setup if you want.
  3. howardp6

    howardp6 Network Guru Member

    Try reversing the airbridge and the WRT54G. Use the WRT54G as an access point, by connectiong the switch to one of the LAN ports of the WRT54G, disabling the DHCP server on the WRT54G and in advanced routing st it as a router and not a gateway. Use the airbridge as a bridge to the WRT54G.
  4. dirtroad

    dirtroad Network Guru Member

    The gateway is set to point to the private IP of my Dlink router in the Airbridge and Linksys. I'm running the current Linksys official firmware right now, but tried DD-WRT v22r2 and it did the same thing.

    Well, that's a good thought, and would likely work, but it would require me to set up another bridge in my network. Remember, I'm testing out equipment that will later be put outdoors. Addind another bridge would add $100-$200 + several hours installing.

    The DSL is @ Location 1.
    The Airbridge needs to link from Location 1 to Location 2.
    The WRT54G needs to be at location 2.
    Location 2 will link to Location 3 & 4.
  5. reber

    reber Network Guru Member

    What if you tried setting up the wrt as a client and not an AP?

    Here's a sample configuration based on my successful wrt-as-client using DD-WRTv22r2. I'm assuming both units share ssids and channels.


    wrt (in client mode)

    lan with DHCP enabled


    Someone else recommended adding a static route on the dlink for the wrt subnet. This appears to be optional in my experience.

    LAN IP--
    Subnet mask--
    Default gateway--
  6. dirtroad

    dirtroad Network Guru Member

    Actually, out of curiosity, I did try that and it did work. However, it is an impractical solution. I need the device deployed at Location 2 to be an access point as it will have 2 clients.

    Making the WRT a client would make me have to put up another device again to do the same job. (I think this is what I'll end up doing, but it is silly because it SHOULD be able to be an AP!)
  7. reber

    reber Network Guru Member

    Yeah, if there's gonna be a wireless client via the wrt, the client solution won't work.

    So it seems that the issue could be related to putting the wrt gateway on the LAN side of the wrt, not the WAN side.

    Maybe try changing wrt routing mode (Advanded Routing) from gateway to router? You could explore that or maybe it just needs a static route defined for the gateway-over-LAN.

    I wonder if a static route isn't the answer. Good luck.

Share This Page