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

connect to another ap

Discussion in 'HyperWRT Firmware' started by kernel_panic, Feb 14, 2005.

  1. kernel_panic

    kernel_panic Network Guru Member

    i want to connect my WRT54G to another ap.
    I´ve changed the wireless setting from AP to client.
    What do i have to do else more to get dhcp address from the other ap.
    i don´t want to use the both ap´s as a wds system because the other side does not provide wds.

  2. tap0utt

    tap0utt Network Guru Member

    you can set it up as lazywds to the other router, if it works.
  3. kernel_panic

    kernel_panic Network Guru Member

    Be sure that u really can read.

    i don´t want to use the both ap´s as a wds system because the other side does not provide wds.
  4. howardp6

    howardp6 Network Guru Member

    The reason lazy WDS was suggested was some limitations on Sveasoft Achemy and Satori firmware. HyperWRT does not have a client mode. There is no transparent bridge available in either firmware. We would probably have to wait for Talisman to get a transparent bridge. You cannot disable NAT on the WRT54G with Achemy or Satori and DHCP and DNS do not pass through NAT. So you must enable your WRT54G as a DHCP Server or use static address for LAN clients and they must be on a different subnet from your othe AP. You have to use a DHCP relay to use your other APs DHCP server feature. You must have a DNS server on the LAN of your WRT54G to do DNS resolution. You have to have a static route setup on your other AP to your WRT54G. Make certain that your encyption keys are the same. Your WRT54G must not be setup as a Gateway and must be setup as an OSF router in advanced routing on your WRT54G. The WLAN port on your WRT54G can be setup as a DHCP Client or with a IP Address outside the range of the DHCP Server on your other AP, but can be set on the same subnet as your othe AP. You must disable the firewall and respond to anonymous Internet Requests on your WRT54G. On advanced management disable 802.X. Save all changes and power down your client for at least thirty seconds. You should be able to see your AP in Wireless Status. The Gateway of your WRT54G must be the IP Address of your other AP.
  5. dellsweig

    dellsweig Network Guru Member

    You can easily configure your WRT54G with hyperwrt to act as an bridge. This has to be done via shell - you can experiment by enabling the telnet daemon and look at the 'wl' command. Once you are happy with your commands - put them in a startup script and you have a wireless bridge (client mode)

Share This Page