Wlan Repeater

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 03:54, 5 February 2009 (edit)
Soulstace (Talk | contribs)
m (Repeater Setup - better wording I think)
← Previous diff
Revision as of 23:41, 4 January 2015 (edit) (undo)
Donny (Talk | contribs)
(Introduction)
Next diff →
(39 intermediate revisions not shown.)
Line 1: Line 1:
 +{{Languages|Repeater}}
You are here: '''[[Main_Page|DD-WRT wiki mainpage]] / [[Linking Routers]] / Wlan Repeater''' You are here: '''[[Main_Page|DD-WRT wiki mainpage]] / [[Linking Routers]] / Wlan Repeater'''
Line 5: Line 6:
__TOC__ __TOC__
-=Introduction=+==Introduction==
-If you got here from Google you may wish to read [[Linking Routers]] first.+If you got here from Google you may wish to read [[Linking Routers]] first. In fact, no matter how you got here, you should look at that page first.
 + 
 +This mode is NOT for WIRED connections between two routers! It is a wireless connection only.
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) 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)
Line 12: Line 15:
*if your host AP is 192.168.1.x, then your repeater could be subnet 192.168.'''2'''.x or 192.168.'''69'''.1 or ... any other unique subnet in your network. If you need a repeater-type solution in the same subnet you are in the wrong place. You need to read [[Linking Routers]] first..! *if your host AP is 192.168.1.x, then your repeater could be subnet 192.168.'''2'''.x or 192.168.'''69'''.1 or ... any other unique subnet in your network. If you need a repeater-type solution in the same subnet you are in the wrong place. You need to read [[Linking Routers]] first..!
-=Preparation=+==Preparation==
You need to know the host router's access credentials: You need to know the host router's access credentials:
*SSID *SSID
Line 18: Line 21:
*its IP address *its IP address
*prepare and verify the DD-WRT to be configured as a repeater *prepare and verify the DD-WRT to be configured as a repeater
-**Note: In order for this work, you should use any V24 build except V24-RC6.2. There were problems with that build!+**Note: '''Make sure you are using a RECENT STABLE BUILD!!! DO NOT USE THE RECOMMENDED BUILDS ON THE DD-WRT HOMEPAGE, those are outdated and buggy. Read the forum (specifically Broadcom) and check the Peacock thread for the latest stable build (either k2.4 or 2.6).'''
**cable-connect your repeater-to-be to a laptop or desktop **cable-connect your repeater-to-be to a laptop or desktop
**install or upgrade the DD-WRT firmware (if required) **install or upgrade the DD-WRT firmware (if required)
**do a 30 sec reset (see [[Hard reset or 30/30/30]]). **do a 30 sec reset (see [[Hard reset or 30/30/30]]).
**verify which chip set your device uses and read Broadcom / Artheros considerations, below **verify which chip set your device uses and read Broadcom / Artheros considerations, below
-**proceed with installation +**proceed with installation
 +==Broadcom Considerations==
 +Note:'''NEVER use v24 SP1. As mentioned above, check the forum stickies (such as the Peacock thread) for the latest recommended stable build.'''
-=Broadcom Considerations=+==Atheros Considerations==
-Note: In order for this work, you should use any V24 build except V24-RC6.2. There were problems with that build!+There is no "Repeater" mode on Atheros units, but you still can use it as repeater, just set the original interface as "client" and get it to connect to your AP, then create a virtual interface to broadcast the new SSID.
-=Atheros Considerations=+==Repeater Setup==
-Anyone? Any? Same as Broadcom?+
- +
-=Repeater Setup=+
To set it up as repeater do the following: To set it up as repeater do the following:
-*Do a 30 sec reset (see [[Hard reset or 30/30/30]]).+#Do a 30 sec reset (see [[Hard reset or 30/30/30]]).
 +#Under '''Wireless -> Basic Settings''':
 +#*Wireless mode: Repeater
 +#*Wireless Network mode: (set to match the host)
 +#*Wireless Network Name (SSID): the SSID of the network you connect to
 +#*Save
 +#*Add 1 virtual interface
 +#*Enter a new (unique) SSID of your choice
 +#*Save
 +#Under '''Wireless -> Wireless Security''':
 +#*Physical Interface wl0:
 +#**Enter the necessary settings to connect to the wlan you'd like to repeat (if no security, leave disabled...but consider enabling security for both host AP and Repeater)
 +#**Save
 +#* Virtual Interface wl0.1:
 +#**Choose the best security mode, which should be WPA2-AES whenever possible.
 +#**Enter a security key
 +#***Note: When using security on both the physical and virtual interfaces, you MUST usually use the same security type, and exactly the same passphrase on both the physical and virtual ssid. If you cannot connect when trying different security or passphrases, make them identical.
 +#**Save
 +#*Note: If you experience problems when setting up for the first time, a leading practice is to configure without any encryption (i.e. setting security to "None") at first, until the unit is confirmed to be working properly, and configuring encryption as a later step.
 +#Under '''Setup -> Basic Setup''':
 +#*Network Setup:
 +#**Here you define the repeater's own subnet
 +#**Set IP address to a different subnet from the Host AP you wish to repeat
 +#**<u>Example:</u> if host AP is 192.168.1.x, assign repeater to 192.168.'''2'''.1
 +#**Set up your DHCP range if you desire
 +#*Save
 +#(Optional but recommended) Under '''Security''':
 +#*Uncheck all items in the "Block WAN Request" section (except Filter Multicast)....THEN disable the SPI firewall
 +#**Note: If you are very concerned about security, a Repeater might still work okay with the SPI firewall enabled. If you decide to leave it enabled but experience problems, keep this step in mind.
 +#*Save
 +#Go back and check each page to ensure that your settings are correct. If they are, hit APPLY. APPLY writes the changes
-'''Under Wireless -> Basic Settings:''' 
-*Wireless mode: Repeater 
-*Wireless Network Name (SSID): the SSID of the network you connect to 
-*Wireless Channel: doesn't matter, but if you want select Auto or the same channel as host AP 
-*Save settings 
-*Add 1 virtual interface 
-*Enter a new (unique) 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, leave disabled...but consider enabling some security on host AP) 
-* Virtual Interface wl0.1: 
-**Choose the best security mode 
-**Enter a different key / credentials from the host AP's 
-***Note: When using WPA on both the physical and virtual interfaces, you may need to use the same passphrase on both. If all else fails, try it. 
-*Save settings 
- 
-'''Under Setup -> Basic Setup:''' 
-*''(Optional)'' Initially, WAN Connection Type will be set 'Automatic Configuration - DHCP'. Once your repeater is working, come back here and select 'Static IP' and change the 'x' from 192.168.1.x to 192.168.1.y (the point being, you may need a '''static address''' to access the repeater's settings from your host subnet). 
-*STP: Disable 
-*Network Setup: 
-**Here you define the repeater's own subnet 
-**Set IP address to a different subnet from the Host AP you wish to repeat 
-**<u>Example:</u> if host AP is 192.168.1.x, assign repeater to 192.168.'''2'''.1 
-**Set up your DHCP range if you desire 
-*Save settings 
- 
-'''Under Security Tab:''' 
-*Uncheck all items in the "Block WAN Request" section (except Filter Multicast)....THEN disable the SPI firewall 
-**Note: If you are very concerned about security, a Repeater might still work okay with the SPI firewall enabled. If you decide to leave it enabled but experience problems, keep this step in mind. 
-*Save Settings 
-'''Under Administration Tab:''' 
-*Enter all other necessary information, change GUI password,... 
-*Click the Apply Settings button 
'''Testing''' '''Testing'''
-*after last reboot has finished, disconnect power and let it cool a bit... (let ARP expire)+*After the Repeater has rebooted, disconnect power and let it cool a bit... (let ARP expire)
-*turn power back on and let it boot+*Turn power back on and let it boot
-*test it, see if you can ping 192.168.'''1'''.x and access an outside web site, say google or yahoo+*See if you can ping 192.168.'''1'''.x and access an outside web site, say Google or Yahoo
'''Footnotes''' '''Footnotes'''
-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.+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.
-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.+If you wish to be able to access your secondary router from devices on your primary LAN, enable Web GUI management in the Remote Access section of the Administration/Management page. You should then be able to access the secondary router by typing in its WAN IP. Setting up a static lease for the device in Services/Services will allow you to always know where it is to access it.
-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 (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.
- +
-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à! Voilà!
-=Tips/Gotcha's/Problems=+==Tips/Gotcha's/Problems==
 + 
-[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+*When MAC Address Cloning is enabled, the Wireless Security Mode of the repeated AP has to match that of the Virtual AP. So if the AP you wish to repeat has WEP encryption you need to use WEP for the Virtual AP. Without MAC Address Cloning, you may select any Wireless Security Mode for the Virtual AP, and it need not match the repeated AP.
-[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.+*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 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.+*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] 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. - 09/17/07+*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 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+*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) - 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+*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
-[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.+*Tests have shown that there is no way to lock a Repeater onto a particular channel - 2/12/2009
-[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.+*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".+*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".
-[EDIT Bib] Wrt54GL1.1 dd-wrt v24 post sp1 build10776. I tried a daisy chain of 4 routers AP-Rpt-Rpt-Clt, G only WPA2, all DHCP client from the previous, all managing it's own subnet with it's own DHCP-DNSMasq Authoritative (192.168.[1-2-3-4].0/24. Worked fine '''even with SPI firewall defaults enabled'''. No issues to manage all nodes from the net with the help of Port Forwardings and Port Range Forwardings.+*I tried a daisy chain of 4 routers AP-Rpt-Rpt-Clt, G-Only WPA2, all DHCP client from the previous, all managing it's own subnet with it's own DHCP-DNSMasq Authoritative (192.168.[1-2-3-4].0/24. Worked fine even with SPI firewall defaults enabled. No issues to manage all nodes from the net with the help of Port Forwardings and Port Range Forwardings. Wrt54GL1.1 dd-wrt v24 post sp1 build10776
 +==See also==
 +[[Repeater Bridge]]
-[[Category: English documentation]]+[[Category:Wlan]]

Revision as of 23:41, 4 January 2015

You are here: DD-WRT wiki mainpage / Linking Routers / Wlan Repeater



Contents


Introduction

If you got here from Google you may wish to read Linking Routers first. In fact, no matter how you got here, you should look at that page first.

This mode is NOT for WIRED connections between two routers! It is a wireless connection only.

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)

  • No setup changes are required to be made to your host-router / AP although some revisions or adjustments may be desirable, as stated below.
  • if your host AP is 192.168.1.x, then your repeater could be subnet 192.168.2.x or 192.168.69.1 or ... any other unique subnet in your network. If you need a repeater-type solution in the same subnet you are in the wrong place. You need to read Linking Routers first..!

Preparation

You need to know the host router's access credentials:

  • SSID
  • the security settings
  • its IP address
  • prepare and verify the DD-WRT to be configured as a repeater
    • Note: Make sure you are using a RECENT STABLE BUILD!!! DO NOT USE THE RECOMMENDED BUILDS ON THE DD-WRT HOMEPAGE, those are outdated and buggy. Read the forum (specifically Broadcom) and check the Peacock thread for the latest stable build (either k2.4 or 2.6).
    • cable-connect your repeater-to-be to a laptop or desktop
    • install or upgrade the DD-WRT firmware (if required)
    • do a 30 sec reset (see Hard reset or 30/30/30).
    • verify which chip set your device uses and read Broadcom / Artheros considerations, below
    • proceed with installation

Broadcom Considerations

Note:NEVER use v24 SP1. As mentioned above, check the forum stickies (such as the Peacock thread) for the latest recommended stable build.

Atheros Considerations

There is no "Repeater" mode on Atheros units, but you still can use it as repeater, just set the original interface as "client" and get it to connect to your AP, then create a virtual interface to broadcast the new SSID.

Repeater Setup

To set it up as repeater do the following:

  1. Do a 30 sec reset (see Hard reset or 30/30/30).
  2. Under Wireless -> Basic Settings:
    • Wireless mode: Repeater
    • Wireless Network mode: (set to match the host)
    • Wireless Network Name (SSID): the SSID of the network you connect to
    • Save
    • Add 1 virtual interface
    • Enter a new (unique) SSID of your choice
    • Save
  3. Under Wireless -> Wireless Security:
    • Physical Interface wl0:
      • Enter the necessary settings to connect to the wlan you'd like to repeat (if no security, leave disabled...but consider enabling security for both host AP and Repeater)
      • Save
    • Virtual Interface wl0.1:
      • Choose the best security mode, which should be WPA2-AES whenever possible.
      • Enter a security key
        • Note: When using security on both the physical and virtual interfaces, you MUST usually use the same security type, and exactly the same passphrase on both the physical and virtual ssid. If you cannot connect when trying different security or passphrases, make them identical.
      • Save
    • Note: If you experience problems when setting up for the first time, a leading practice is to configure without any encryption (i.e. setting security to "None") at first, until the unit is confirmed to be working properly, and configuring encryption as a later step.
  4. Under Setup -> Basic Setup:
    • Network Setup:
      • Here you define the repeater's own subnet
      • Set IP address to a different subnet from the Host AP you wish to repeat
      • Example: if host AP is 192.168.1.x, assign repeater to 192.168.2.1
      • Set up your DHCP range if you desire
    • Save
  5. (Optional but recommended) Under Security:
    • Uncheck all items in the "Block WAN Request" section (except Filter Multicast)....THEN disable the SPI firewall
      • Note: If you are very concerned about security, a Repeater might still work okay with the SPI firewall enabled. If you decide to leave it enabled but experience problems, keep this step in mind.
    • Save
  6. Go back and check each page to ensure that your settings are correct. If they are, hit APPLY. APPLY writes the changes


Testing

  • After the Repeater has rebooted, disconnect power and let it cool a bit... (let ARP expire)
  • Turn power back on and let it boot
  • See if you can ping 192.168.1.x and access an outside web site, say Google or Yahoo

Footnotes

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.

If you wish to be able to access your secondary router from devices on your primary LAN, enable Web GUI management in the Remote Access section of the Administration/Management page. You should then be able to access the secondary router by typing in its WAN IP. Setting up a static lease for the device in Services/Services will allow you to always know where it is to access it.

But for the pièce de résistance, go into the Host WLAN router's web GUI (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à!

Tips/Gotcha's/Problems

  • When MAC Address Cloning is enabled, the Wireless Security Mode of the repeated AP has to match that of the Virtual AP. So if the AP you wish to repeat has WEP encryption you need to use WEP for the Virtual AP. Without MAC Address Cloning, you may select any Wireless Security Mode for the Virtual AP, and it need not match the repeated AP.
  • 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.
  • 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.
  • 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.
  • 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) - 09/17/07
  • 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
  • Tests have shown that there is no way to lock a Repeater onto a particular channel - 2/12/2009
  • 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".
  • I tried a daisy chain of 4 routers AP-Rpt-Rpt-Clt, G-Only WPA2, all DHCP client from the previous, all managing it's own subnet with it's own DHCP-DNSMasq Authoritative (192.168.[1-2-3-4].0/24. Worked fine even with SPI firewall defaults enabled. No issues to manage all nodes from the net with the help of Port Forwardings and Port Range Forwardings. Wrt54GL1.1 dd-wrt v24 post sp1 build10776

See also

Repeater Bridge