Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:user-guide:wifi:atheroswds [2018/02/25 14:41] – ↷ Links adapted because of a move operation | docs:guide-user:network:wifi:atheroswds [2024/06/24 06:19] (current) – moved bluewavenet | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | + | ||
| - | Most OpenWrt supported wireless drivers support since kernel 2.6 the AP-to-STA WDS mode to connect two or more devices using wireless bridging to form one common broadcast domain. | + | |
| - | + | ||
| - | With this configuration you will be able to wirelessly connect a remote wireless OpenWrt device (acting as the wireless station) to a local wireless OpenWrt point (acting as the wireless access point) and the wired devices connected to both devices will be on the same network and broadcast domain. Other wireless client devices can continue to connect to the wireless access point as before. | + | |
| - | + | ||
| - | The method below is a layer 2 transparent bridge. All broadcast packets (such as DHCP requests) will be sent in both directions over the wireless bridge and the original source MAC address of the wired devices on both sides are preserved even over the bridge. The wiki article [[doc/howto/ | + | |
| - | + | ||
| - | ===== Configuration ===== | + | |
| - | + | ||
| - | * Tested | + | |
| - | * Tested with OpenWrt 15.05 using two TP-LINK TL-WR1043ND | + | |
| - | * Tested with OpenWrt 15.05.1 using a Netgear WNDR3700v4 as the access point and a Nexx WT3020 as the client bridge device. | + | |
| - | + | ||
| - | With both [[docs: | + | |
| - | + | ||
| - | ==== Using SSH ==== | + | |
| - | + | ||
| - | === The Access Point === | + | |
| - | + | ||
| - | Connect to the router that will serve as the wireless access point over SSH. This is the device that connects to the internet or the main network using a wired connection. Ensure that the device is already set up as a normal wireless access point with a SSID, channel selection, WPA2 encryption as desired, etc. and that normal wireless clients can connect to it fine. | + | |
| - | + | ||
| - | Only one change is needed from a normal wireless access point configuration. | + | |
| - | + | ||
| - | Once logged in, edit the [[docs: | + | |
| - | + | ||
| - | Once that is done, save the file and reboot the device to restart all settings. | + | |
| - | + | ||
| - | Normal wireless clients should be able to connect to the wireless access point exactly as they did before and access the Internet. | + | |
| - | + | ||
| - | This is an example from / | + | |
| - | + | ||
| - | < | + | |
| - | config wifi-device ' | + | |
| - | option type ' | + | |
| - | option macaddr ' | + | |
| - | option hwmode ' | + | |
| - | option htmode ' | + | |
| - | list ht_capab ' | + | |
| - | list ht_capab ' | + | |
| - | option txpower ' | + | |
| - | option channel ' | + | |
| - | option country ' | + | |
| - | + | ||
| - | config wifi-iface | + | |
| - | option device ' | + | |
| - | option network ' | + | |
| - | option ssid ' | + | |
| - | option encryption ' | + | |
| - | option key ' | + | |
| - | option mode ' | + | |
| - | option wds ' | + | |
| - | </ | + | |
| - | + | ||
| - | After rebooting, the " | + | |
| - | + | ||
| - | The new wlan.staN interface WILL NOT be bridged by default with the originating wlan interface if that interface is not itself part of a bridge, | + | |
| - | If in your setup the AP interface is not already part of a bridge you will need to create a new bridge interface and associate only the AP wlan interface to it. In this case hostapd will automatically add any new wlan.staN interface to the bridge. | + | |
| - | + | ||
| - | === The remote wireless station | + | |
| - | + | ||
| - | Initially connect to the router that will server as remote wireless station using an Ethernet cable. If you haven' | + | |
| - | + | ||
| - | The first step is preparing the device for the bridging. | + | |
| - | + | ||
| - | If this is a new OpenWrt setup, a DHCP server is enabled on the lan interface of the device by default. This needs to be disabled before the device is connected to the production network (assuming the production network already has DHCP set up). To do so, edit the [[docs: | + | |
| - | + | ||
| - | Following this, reconfigure the lan interface to have another address than the default static IP assignment of 192.168.1.1. Edit the [[docs: | + | |
| - | + | ||
| - | Alternatively, | + | |
| - | + | ||
| - | < | + | |
| - | config interface ' | + | |
| - | option ifname ' | + | |
| - | option type ' | + | |
| - | option proto ' | + | |
| - | </ | + | |
| - | + | ||
| - | __**NOTE: | + | |
| - | + | ||
| - | Once those steps are completed, we can setup the actual wireless link. | + | |
| - | + | ||
| - | Edit the [[docs: | + | |
| - | + | ||
| - | Further down in the same file, modify the '' | + | |
| - | + | ||
| - | This is an example from / | + | |
| - | + | ||
| - | < | + | |
| - | config wifi-device ' | + | |
| - | option type ' | + | |
| - | option macaddr ' | + | |
| - | option hwmode ' | + | |
| - | option htmode ' | + | |
| - | list ht_capab ' | + | |
| - | list ht_capab ' | + | |
| - | list ht_capab ' | + | |
| - | list ht_capab ' | + | |
| - | list ht_capab ' | + | |
| - | option txpower ' | + | |
| - | option country ' | + | |
| - | option channel ' | + | |
| - | option disabled ' | + | |
| - | + | ||
| - | config wifi-iface | + | |
| - | option device ' | + | |
| - | option network ' | + | |
| - | option mode ' | + | |
| - | option wds ' | + | |
| - | option ssid ' | + | |
| - | option encryption ' | + | |
| - | option key ' | + | |
| - | </ | + | |
| - | + | ||
| - | See the [[doc: | + | |
| - | + | ||
| - | Disconnect the device from the wired network and reboot the device without any wired connection. | + | |
| - | + | ||
| - | The device should boot and automatically connect wirelessly to the access point. **Wait until the client bridge device associates with the access point. This can take 1-2 minutes for the association to happen.** Once this has happened, the **wired interface (e.g. eth0)** should succeed in getting a DHCP address through the new wireless bridge connection. Note that the wireless interface itself on the remote client bridge device does not get an IP address as it is now acting as a transparent bridge. | + | |
| - | + | ||
| - | Any //wired devices// connected via Ethernet to the LAN ports on the remote client bridge device should now be transparently bridged into the main network over the wireless link. | + | |
| - | + | ||
| - | **For wireless connection, one additional step is required: | + | |
| - | + | ||
| - | Create a //new wireless interface// | + | |
| - | + | ||
| - | ==== LuCI ==== | + | |
| - | + | ||
| - | Everything shown in the manual SSH configuration section above should be possible using LuCI in OpenWrt 12.09. | + | |
| - | + | ||
| - | === The Access Point === | + | |
| - | For the wireless access point, just set the wireless mode to " | + | |
| - | + | ||
| - | === The remote wireless station === | + | |
| - | + | ||
| - | On the LAN Interface, change the default IP to a different one within the target subnet and disable the DHCP server. ([[http:// | + | |
| - | + | ||
| - | + | ||
| - | Join the previously created wireless network and when asked, set the firewall zone to " | + | |
| - | + | ||
| - | For the remote wireless bridge device, the wireless mode should be " | + | |
| - | + | ||
| - | ===== Old Stuff ===== | + | |
| - | + | ||
| - | Relevant configuration files: | + | |
| - | + | ||
| - | * [[docs: | + | |
| - | * [[docs: | + | |
| - | * [[docs: | + | |
| - | + | ||
| - | + | ||
| - | Multiple //WDS Stations// can connect to a single //WDS Access Point//. | + | |
| - | + | ||
| - | * On the Access Point, add '' | + | |
| - | * On the Client, set '' | + | |
| - | *To create a repeater, add a WDS Access Point along with the WDS Station on the client, | + | |
| - | + | ||
| - | On MAC80211 OpenWRT use 4 address (option wds 1) (with ap or sta mode) and not repeater mode. See also [[http:// | + | |
| + | This document has now moved. Please see: | ||
| + | [[: | ||