Station Mode
From DD-WRT Wiki
Revision as of 07:31, 26 June 2010 (edit) Phuzi0n (Talk | contribs) (cleanup intro) ← Previous diff |
Revision as of 18:01, 17 December 2015 (edit) (undo) Donny (Talk | contribs) (→Client Mode Setup - fixed gateeway info) Next diff → |
||
Line 3: | Line 3: | ||
==Introduction== | ==Introduction== | ||
+ | |||
+ | This mode is NOT for WIRED connections between two routers! It is a wireless connection between two routers only. | ||
+ | |||
A router in Client Mode connects to another wireless Access Point (the host router). It uses its wireless connection as the WAN interface, and shares the internet connection only to the LAN ports. It is not seen as an access point by laptops or other computers scanning for AP's and does not accept wireless connections from client devices. The AP is not required to be running DD-WRT firmware. | A router in Client Mode connects to another wireless Access Point (the host router). It uses its wireless connection as the WAN interface, and shares the internet connection only to the LAN ports. It is not seen as an access point by laptops or other computers scanning for AP's and does not accept wireless connections from client devices. The AP is not required to be running DD-WRT firmware. | ||
Line 11: | Line 14: | ||
To have computers connected to both routers (main and secondary) and co-exist in the same subnet, set up DD-WRT as a [[Client Bridged|Client Bridge]], [[Repeater Bridge]] or use [[WDS_Linked_router_network|WDS]]. Further explanation of bridging modes is in the [[Glossary]]. | To have computers connected to both routers (main and secondary) and co-exist in the same subnet, set up DD-WRT as a [[Client Bridged|Client Bridge]], [[Repeater Bridge]] or use [[WDS_Linked_router_network|WDS]]. Further explanation of bridging modes is in the [[Glossary]]. | ||
+ | ==Client Mode Setup== | ||
+ | The Router/AP that you are trying to connect to is the primary router. The Router you are configuring is the client router. You don't need to worry about the primary router as long as you set your client LAN IP address to a different subnet. What this means is, if the primary router has an IP of 192.168.'''A'''.x, you need to set the client router to an IP of 192.168.'''B'''.x. Most primary routers will be at 192.168.1.1, or 192.168.0.1. So, when you are configuring your client router, set it to 192.168.2.x. | ||
- | + | With that in mind, here is how to configure it: | |
- | + | # Download the '''current''' recommended build for your router. Check the forum for your chipset to find recommended builds and general information related to your hardware. If you are using a Broadcom based router, read the [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486 peacock thread] prior to starting. DO NOT USE SP1! | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | # Download the '''current''' recommended build for your router. If you are using a | + | |
# Do a HARD reset on your router. | # Do a HARD reset on your router. | ||
# Connect a cable from your computer to the LAN port on your router. | # Connect a cable from your computer to the LAN port on your router. | ||
- | # Set your computer to a static IP address | + | # Set your computer to a static IP address (e.g. 192.168.1.7) |
- | # | + | # Open a web browser and connect to 192.168.1.1 to view the DD-WRT GUI. |
- | # You should be asked to change your password and username. | + | # You should be asked to change your password and username. Carefully type these in. If you aren't asked for a password and username, do a hard reset, this time doing it properly! Hit change password. |
- | # | + | # FIRST go to Wireless -> Wireless Security and enter the Security Mode and other key information that matches your primary router that you will be connecting to over wireless. |
# Hit SAVE (not apply) | # Hit SAVE (not apply) | ||
- | # | + | # NEXT go to the Wireless -> Basic Settings and change the Wireless Mode to Client. |
- | # | + | # On that same tab set the Wireless Network Name (SSID) to exactly the same SSID as your primary router you will be connecting to over wireless. Make sure spelling and capitalization match. ''Note: If there are multiple routers broadcasting the same SSID, and you would like to connect to a specific one (IE, the primary router, instead of the repeater), enable MAC Filtering on the Wireless Tab, and add the MAC Address of the correct Access Point. The MAC Address can be found on the "Site Survey" page, linked from the "Wireless" Sub-tab of the "Status" Tab.'' - Conjur |
- | # Set the correct ack timing in | + | # ''(Optional)'' Set the correct ack timing in meters. (Where?) |
# Hit SAVE (not apply) | # Hit SAVE (not apply) | ||
- | # | + | # NEXT go to Setup -> Basic Setup and change Connection Type to Automatic Configuration - DHCP (most likely, but see NOTE below). |
- | + | # On that same tab in the Network Setup section set the Local IP Address to 192.168.2.1 (Your Client subnet '''MUST''' differ from the Primary Router subnet!). | |
- | # | + | # Set your gateway to the IP address of your client router e.g. 192.168.2.1 |
- | # | + | # ''(Optional)'' Set Static DNS servers in the Network Address Server Settings section if your WAN type does not provide them or you want to use different ones than the AP provides. |
- | # Change your | + | # ''(Recommended)'' Change your Time Zone and DST to match where you are. |
+ | # ''(Optional)'' Set a Server IP/Name for in Time Setting section for NTP (it will use a hidden default server if you leave it blank). | ||
# Hit SAVE (not apply) | # Hit SAVE (not apply) | ||
- | # | + | # ''(Optional)'' Go to Security -> Firewall and disable the SPI Firewall if you do not need to worry about security between the AP and Client router. |
- | + | ||
# Hit Apply. | # Hit Apply. | ||
- | # Set your computer back to auto IP and auto DNS if | + | # Set your computer back to auto IP and auto DNS if you like. You will get a DHCP address from the router. |
- | You are done. | + | You are done and the Client router should connect to the AP within a minute or so. You may need to unplug the router for 17 seconds if the router doesn't reset. After you ensure that it does connect and work properly then you may configure any other settings you wish to (Virtual Interface for wireless connection for example). |
- | + | NOTE: If the client router is externally managed, such as in a college dorm etc., you should Go to Setup -> Basic Setup and set the WAN port protocol to what you need for the AP (mostly static, dhcp or pppoe). This is the setting that is bonded to the Wifi interface. Fill in the needed info provided by your ISP if this AP is externally managed. Note: This is what a computer (wired or wireless) connected to the ROUTER would use to gain access to the network, not to be confused with the settings required to gain access to the WAN by the ROUTER. Also note that the device should be in GATEWAY MODE instead of ROUTER mode, otherwise Masquerade/NAT does not happen. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
==Troubleshooting== | ==Troubleshooting== | ||
- | ===Moving from previous configuration=== | ||
- | If you are moving from a previously configured WDS setting to Client Mode Wireless, it is '''Extremely Important''' to note that if the MAC address of CLIENT was in the WDS configuration for ROUTER, and is marked as "disabled", it will fail, regardless of how well you set up CLIENT. | ||
- | |||
- | Also, make sure the WDS settings are completely clear in CLIENT as well. | ||
- | |||
- | As an example, if ROUTER and CLIENT were both WDS nodes, and their MAC addresses were in the WDS settings for each other, this setup will '''FAIL''' unless you remove the MAC address of CLIENT from ROUTER's WDS configuration. Just disabling it will not be enough. | ||
- | |||
- | ===Old firmware=== | ||
- | If you still can't connect wirelessly to your wireless access point router in CLIENT MODE and your access point has an early firmware version more than 1 year old, you may have to upgrade the accesss point's firmware. | ||
- | |||
- | ===Port forwarding to the client subnet=== | ||
- | ''When port forwarding is needed, it will need to be configured at both routers, not just the host router'' - this is not my experience (v23sp2). The only way I could get port forwarding to work both internally and externally was to configure it only on the host router ''and'' running the following command: | ||
- | |||
- | :iptables -t nat -R POSTROUTING 3 -s 192.168.0.0/16 -d 192.168.0.0/16 -j MASQUERADE | ||
- | |||
- | Without this iptables command, it would only work externally. I got this tip in the forums, but received no real explanation as to why it was needed. | ||
- | |||
- | ===Resolving DNS lookup Problems=== | ||
- | The above instructions didn't work for me as far as routing my traffic off of the client router. In other words, I could continue to hit the DD-WRT router and even ping the remote router (at 192.168.1.1) but I couldn't ping any external addresses. I had to make the following changes in the Setup > Basic Setup tab: | ||
- | |||
- | |||
- | Wireless Setup.Disable STP (not sure if this is actually necessary, but my working config has it disabled) | ||
- | |||
- | '''Step 3.15''' Network Setup.Gateway = 192.168.1.1 (Same as assumption #2) | ||
- | ***CONFIRMED to work on a WRT54G v3 Apr 6, 2009 *** | ||
- | |||
- | '''Step 3.16''' Network Setup.Local DNS = 192.168.1.1 (Same as assumption #2) | ||
- | |||
- | |||
- | As soon as I made these changes everything worked. | ||
- | |||
- | Note that this setup enables Xbox 360 to retrieve a DHCP address and access Live servers (other DD-WRT setups for "bridging" don't seem to work as they fail in relaying DHCP and DNS servers). | ||
- | |||
- | You shouldn't have to make the changes suggested in the next section, "Destination Host Unreachable", if you stick to the main steps and the tweaks listed here. | ||
- | |||
- | ==="Destination Host Unreachable" when pinging internet hosts=== | ||
- | I followed the exact setup steps here, using a Linksys WRT54G v8 router with DD-WRT v24 RC-4 Micro. After setting up, when I had a computer just connected to the CLIENT, I could successfully ping and connect to the ROUTER and the CLIENT, and could get DNS resolution for internet addresses (e.g. www.yahoo.com), but trying to ping them from a windows command line would give "Destination Host Unreachable" from the CLIENT. | ||
- | |||
- | After a lot of trial and error, the fix that worked for me was to disable all the VLAN's on the CLIENT (setup > VLANs > uncheck all the checkboxes in Row VLAN 0 (which had 1/2/3/4 checked) and VLAN 1 (which had W checked). This immediately fixed the problem. Note this caused me to lose the ability to connect to the box and required a reset to recover. | ||
- | |||
- | I am not a routing or DD-WRT expert by any means, so if doing this has some gruesome side effect, please note it here! I saw in the forums that several other people experienced the same symptom, but saw no posted solutions anywhere for it. Hopefully this helps some people. | ||
- | |||
- | I had a similar problem when trying to get any kind of encryption to work (worked fine without). I would lose the ability to ping my primary router, though I could "join" the site. I'm working with a D-Link DI-624 primary router provided by Verizon (FIOS), and a WRT54G as a client. Note the D-Link is modified so you can't update the firmware. I FINALLY got WEP encryption working after setting Wireless>Advanced Settings>CTS Protection Mode from Disable to Auto (this was the setting on the primary router). Still couldn't get WPA-PSK working though. | ||
- | + | If following the instructions does not seem to work, in 90% of the cases, it is a problem with encryption. Disable encryption on the primary router and try the setup again to see if this is the case. Use WPA2-AES encryption only with dd-wrt. WEP will often work as well, but it is not a secure form of encryption. Using proper encryption and following the instructions WILL work, so if it doesn't you need to re-exxamine the instructions and see what you have done incorrectly. Do a hard reset and start over. | |
- | =External Links= | + | ==External Links== |
- | http:// | + | *http://www.dd-wrt.com/wiki/index.php?title=Client_Mode&oldid=34051 - Old wiki instructions. |
- | http://www.wi-fiplanet.com/tutorials/article.php/3639271 graphical representation | + | *http://www.wi-fiplanet.com/tutorials/article.php/3639271 graphical representation |
[[Category:Wlan]] | [[Category:Wlan]] | ||
[[Category:Basic tutorials]] | [[Category:Basic tutorials]] |
Revision as of 18:01, 17 December 2015
You are here: DD-WRT wiki mainpage / Linking Routers / Client Mode
Contents |
Introduction
This mode is NOT for WIRED connections between two routers! It is a wireless connection between two routers only.
A router in Client Mode connects to another wireless Access Point (the host router). It uses its wireless connection as the WAN interface, and shares the internet connection only to the LAN ports. It is not seen as an access point by laptops or other computers scanning for AP's and does not accept wireless connections from client devices. The AP is not required to be running DD-WRT firmware.
The main router and secondary router (DD-WRT client mode) are on separate subnets. NAT is used between the routers. Thus, when port forwarding is needed it must be configured at both routers — not just on the main (host) router.
The router in Client Mode must use its own DHCP server to give out IP numbers, Gateway and DNS server to the devices connected to its LAN ports.
To have computers connected to both routers (main and secondary) and co-exist in the same subnet, set up DD-WRT as a Client Bridge, Repeater Bridge or use WDS. Further explanation of bridging modes is in the Glossary.
Client Mode Setup
The Router/AP that you are trying to connect to is the primary router. The Router you are configuring is the client router. You don't need to worry about the primary router as long as you set your client LAN IP address to a different subnet. What this means is, if the primary router has an IP of 192.168.A.x, you need to set the client router to an IP of 192.168.B.x. Most primary routers will be at 192.168.1.1, or 192.168.0.1. So, when you are configuring your client router, set it to 192.168.2.x.
With that in mind, here is how to configure it:
- Download the current recommended build for your router. Check the forum for your chipset to find recommended builds and general information related to your hardware. If you are using a Broadcom based router, read the peacock thread prior to starting. DO NOT USE SP1!
- Do a HARD reset on your router.
- Connect a cable from your computer to the LAN port on your router.
- Set your computer to a static IP address (e.g. 192.168.1.7)
- Open a web browser and connect to 192.168.1.1 to view the DD-WRT GUI.
- You should be asked to change your password and username. Carefully type these in. If you aren't asked for a password and username, do a hard reset, this time doing it properly! Hit change password.
- FIRST go to Wireless -> Wireless Security and enter the Security Mode and other key information that matches your primary router that you will be connecting to over wireless.
- Hit SAVE (not apply)
- NEXT go to the Wireless -> Basic Settings and change the Wireless Mode to Client.
- On that same tab set the Wireless Network Name (SSID) to exactly the same SSID as your primary router you will be connecting to over wireless. Make sure spelling and capitalization match. Note: If there are multiple routers broadcasting the same SSID, and you would like to connect to a specific one (IE, the primary router, instead of the repeater), enable MAC Filtering on the Wireless Tab, and add the MAC Address of the correct Access Point. The MAC Address can be found on the "Site Survey" page, linked from the "Wireless" Sub-tab of the "Status" Tab. - Conjur
- (Optional) Set the correct ack timing in meters. (Where?)
- Hit SAVE (not apply)
- NEXT go to Setup -> Basic Setup and change Connection Type to Automatic Configuration - DHCP (most likely, but see NOTE below).
- On that same tab in the Network Setup section set the Local IP Address to 192.168.2.1 (Your Client subnet MUST differ from the Primary Router subnet!).
- Set your gateway to the IP address of your client router e.g. 192.168.2.1
- (Optional) Set Static DNS servers in the Network Address Server Settings section if your WAN type does not provide them or you want to use different ones than the AP provides.
- (Recommended) Change your Time Zone and DST to match where you are.
- (Optional) Set a Server IP/Name for in Time Setting section for NTP (it will use a hidden default server if you leave it blank).
- Hit SAVE (not apply)
- (Optional) Go to Security -> Firewall and disable the SPI Firewall if you do not need to worry about security between the AP and Client router.
- Hit Apply.
- Set your computer back to auto IP and auto DNS if you like. You will get a DHCP address from the router.
You are done and the Client router should connect to the AP within a minute or so. You may need to unplug the router for 17 seconds if the router doesn't reset. After you ensure that it does connect and work properly then you may configure any other settings you wish to (Virtual Interface for wireless connection for example).
NOTE: If the client router is externally managed, such as in a college dorm etc., you should Go to Setup -> Basic Setup and set the WAN port protocol to what you need for the AP (mostly static, dhcp or pppoe). This is the setting that is bonded to the Wifi interface. Fill in the needed info provided by your ISP if this AP is externally managed. Note: This is what a computer (wired or wireless) connected to the ROUTER would use to gain access to the network, not to be confused with the settings required to gain access to the WAN by the ROUTER. Also note that the device should be in GATEWAY MODE instead of ROUTER mode, otherwise Masquerade/NAT does not happen.
Troubleshooting
If following the instructions does not seem to work, in 90% of the cases, it is a problem with encryption. Disable encryption on the primary router and try the setup again to see if this is the case. Use WPA2-AES encryption only with dd-wrt. WEP will often work as well, but it is not a secure form of encryption. Using proper encryption and following the instructions WILL work, so if it doesn't you need to re-exxamine the instructions and see what you have done incorrectly. Do a hard reset and start over.
External Links
- http://www.dd-wrt.com/wiki/index.php?title=Client_Mode&oldid=34051 - Old wiki instructions.
- http://www.wi-fiplanet.com/tutorials/article.php/3639271 graphical representation