WRT54G Client Not Networking

Discussion in 'Networking Issues' started by mute-, Aug 17, 2006.

  1. mute-

    mute- LI Guru Member

    Alright so heres my setup, i have a Modem -> Wireless Dlink Router(DHCP/, And i just got this WRT54G setup with dd-wrt.

    I was following the basics of this setup here, http://tinyurl.com/hdabq.

    So for the WRT54G, i set its ip to Also set its gateway to dlink). And i went into wireless settings and set it to client mode and changed the ssid to the dlinks ssid (dlink). Then i sshed into the wrt and did a wl join dlink, and do a wl status to verify its connected. also on the dlink routers status page it shows the wrt's mac wirelessly connected. But when i try to ping anything via ssh on the wrt everything fails.
  2. jgutz20

    jgutz20 Network Guru Member

    are you trying to setup the WRT as a wireless repeater or bridge? what version of WRT do you have?
  3. mute-

    mute- LI Guru Member

    I have 23 SP1
  4. mute-

    mute- LI Guru Member

    right well i got it to work using this...dont understand it but whatever

    The simple way to turn a WRT into a WET:

    Starting with factory defaults on DD-WRT V22prefinal5
    on the setup basic tab - make sure internet is either disabled or set to automatic
    Make sure STP is OFF!! you will have problems if it is turned on!
    EDIT: [ Make sure you turn off the firewall under security ]
    set the local ip address to one outside of the main router's DHCP scope (I have a Dlink DI-524 with and address of and scope of, my WRT is at
    Make sure you set the WRT to AP mode (otherwise the bridge is broken between the lan and wireless)
    set your SSID, channel etc..
    turn off the DHCP server on the WRT
    turn on the telnet server on the Administration Tab
    reboot the wrt..
    set your client pc to an address outside of your main routers dhcp scope temporarily ( the bridge is not up yet)
    telnet into the WRT and issue the following commands:

    ~ # wl ap 0 <-- this turns off the AP Mode
    ~ # wl wet 1 <-- this turns wireless bridge on (aka WET54 )
    ~ # wl join <SSID> <network key>

    after a few seconds the bridge will come up. Set your client PC back to DHCP, and the main router will give you an address. If you need to save your bridge configuration, you can set it to the rc_startup variable like this:

    ~ # nvram set rc_startup="wl ap 0;wl wet 1;wl join <ssid> <key>"
    ~ # nvram commit

    I recommend getting the bridge to work with no security first, then add wep after that - sorry no idea how to get WPA to work as yet (the real WET54G only supports WEP)

  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