Wlan Repeater

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 00:00, 8 July 2008 (edit)
Geetek (Talk | contribs)

← Previous diff
Revision as of 22:42, 17 August 2008 (edit) (undo)
Soulstace (Talk | contribs)
m (added hard reset procedure)
Next diff →
Line 2: Line 2:
To set it up as repeater do the following: To set it up as repeater do the following:
-*Do a 30 sec reset+*Do a 30 sec reset (see [[Hard reset or 30/30/30]]).
'''Under wireless->basic settings:''' '''Under wireless->basic settings:'''
*Wireless mode: repeater *Wireless mode: repeater

Revision as of 22:42, 17 August 2008

Note: In order for this work, you should have the last Release Candidate (RC7), or V24-final. But not RC6.2!

To set it up as repeater do the following:

Under wireless->basic settings:

  • Wireless mode: repeater
  • Wireless Network Name (SSID): the ssid of the network you connect to.
  • Wireless Channel: auto
  • Save Settings
  • Add 1 virtual interface
  • Enter an SSID of your choice
  • Network configuration: bridged
  • Save settings

Under Wireless > Wireless Security

  • Physical Interface wl0 enter the necessary settings to connect to the wlan you'd like to repeat (if none, select disabled)
  • Virtual Interfaces wl0.1 enter the encryption type as well as the password of your wlan (disabled for no encryption)
  • Save Settings

Under Setup->Basic Setup:

  • Set IP address to a different subnet from the Host AP you wish to repeat
  • Set up your DHCP range if you desire
  • Checkmark "Use DNSmasq for DHCP", "Use DNSmasq for DNS", and "DHCP Authoritative"
  • Save Settings

Under Security Tab

  • Uncheck all items in the "Block WAN Request" section....THEN disable the SPI firewall
  • Save Settings

Under Administration Tab

  • Enter all other necessary information, change gui password,...
  • Click the Apply button then click Reboot


[EDIT-Redhawk] If you use Static Leases to control your Repeater's IP addresses...please note that with the new RC6 builds the WLAN MAC address is now duplicated to the WAN MAC address. This will require you to change the MAC address value in the Static Lease section on the Host AP (if you use this mode for your managed network)....RC5 and earlier used MAC+1 for Wireless...with RC6+ it will now be MAC+2

[EDIT-Redhawk] I have seen on some networks where repeater mode will not provide a reliable connection if the STP function is Enabled on the Basic Setup page...Set it to Disabled and see if your connection improves.

[EDIT-Redhawk] I had a problem with Post RC7-9068 builds where if you would manually disconnect from the Virtual SSID and try to reconnect, it would not. Power cycling the router was the only work around. Make sure that the "Use DNSmasq for DHCP", "Use DNSmasq for DNS", and "DHCP Authoritative" are all check marked on the Setup>>Basic Setup page to correct this.

[EDIT-Redhawk] You need to be on a different subnet then the host AP you are connecting to (Physical network)...try setting it to something like 192.168.69.1 on the Setup>>Basic Setup tab (if a physical of 192.168.1.1 is used for the host AP) - see first note below....Note2 probably won't work. - 09/17/07

[EDIT-Redhawk] You also must uncheck all options for Block WAN Requests on the Security Tab....Then Disable the SPI firewall. If you don't, repeater mode won't work. - 09/17/07

[EDIT-Redhawk] - I found another gotcha....If the host AP settings Wireless>>Basic Settings>>Wireless Network Mode is set to "G-only" then your repeater must also be set the same way....otherwise you will not make the connection from the repeater side - 09/22/07

This is by far the EASIEST and ONLY working solution found so far after testing on multiple units. Works with stock firmware from Buffalo and WRT on any Linksys V2.4 (with V1.1 it works also)

Note: With me this only worked after changing the IP adress of the repeater to another subnet under Setup > Basic Setup, for example: host/ router: 192.168.1.1 repeater: 192.168.69.1

Note 2: For me it worked after changing the IP address of the repeater to host not .1 but .8 say, as follows, if host is 192.168.11.1 repeater is 192.168.11.8 (any number at the end but 1).

[EDIT Stuckeymax] Using the Linksys WRT54GL flashed with DD-WRT.v24 beta, I found that using a different subnet, such as 192.168.2.1 AND setting this same address (192.168.2.1, in this example) into both Gateway AND Local DNS boxes on the Setup/Basic Setup/Network Setup section, I get perfect operation. Note that Virtual Interface (Repeater SSID) can be the same as the Physical Interface (SSID of the Host or originating WLAN, i.e. the signal you are repeating). If Host and Repeater SSID are the same, a wireless client near the repeater could wander between linkage with the repeater and linkage with the Host WLAN some distance away; this could lead to inconsistent signal strength. Therefore, unless having additional SSIDs creates confusion for non-technical users, the preferred setup mode is to have a repeater SSID that is distinct from the Host SSID, perhaps a locally significant name.

Also, use the "Apply" button instead of "Save" when you finish with each page. "Save" should work, but I don't think it does. "Apply" works, i.e. saves the information just entered.

Also, go to the Wireless/Wireless Security page, check the WEP or WPA settings if any, then click "Apply." This should not be necessary, but I saw one instance where it seemed to make a difference.

Be sure to reboot when you are done. When the unit has logged onto the Host WLAN and has begun repeating its signal, you will see the DHCP address (generally in the 192.168.1.100-150 range) in the upper right-hand corner as the WAN address. As long as you see quad zeros up there (0.0.0.0), you are not linked and are not repeating. You might click the "reload) button on your browser once or twice to make sure the WAN IP is fresh while you are making changes. Make sure your repeater is within radio range of your host network; the WRT54GL has a great radio in it, and if you want heat, you can go to Wireless/Advanced Settings and jack Xmit Power up as high as 150 and the transmit PA will still run linear enough to support 54 MBit/sec OFDM. Once you are up and running (repeating), you can get to the repeater's web GUI from your local intranet by entering its private IP address in your web browser.

But for the pièce de résistance, go into the Host WLAN router's web GUI (Gaming & Applications/Port Forwarding on DD-WRT.v23; NAT/QoS/Port Forwarding on DD-WRT.v24 beta) and set up a port forward so you can check on and fully access and control your new repeater from Outside, i.e. via the Internet. Look up the address that DHCP has assigned to your new repeater (the name you entered in Setup/Basic Setup/Optional Settings/Host Name will appear in the DHCP clients table of the Host router under Status/Sys-Info), and write it down. Then go to Port Forwarding and click "Add." Make the forwarded port (Port from) something you can remember easily, like 8128 if you found your repeater on 192.168.1.128, for example. Click Both for Protocol, enter the IP private IP address of your repeater in the IP Address box, enter Port 80 (http default) in the "Port to" box. Or if you want to be tricky, enter something besides 80, but just be sure this matches the active Web GUI port number on your repeater). Lastly, be sure to check "Enable," and then click "Save Settings" (v23) or "Apply" (v24 beta). Then go Outside, and take a look at your main WLAN router at its public IP address (or DDNS link), and then take a peek at your repeater's Web GUI on the same address (or DDNS link) followed by :8128, e.g. http://yourwlan.dyndns.org/ for your Host router and http://yourwlan.dyndns.org:8128/ for the repeater. But you knew that already.

Voilà!

[EDIT milican] I was not able to get online with the Gateway and the Local DNS containing my router's IP as Stuckeymax suggested. Instead I left them as 0.0.0.0 and all was good.

Also take note of the fact that all repeaters, including this Wlan Repeater mode, will sacrifice half of the bandwidth available from the primary router for clients wirelessly connected to the repeater. This is a result of the repeater taking turns talking to not just one partner, but to two, and having to relay the traffic between them. As long as your bandwidth requirements are within this halved bandwidth amount there will be little or no reduction in "speed".