There is a WiKi Page which describes how to do this. However, in the section Access Point (& then 3 paras down) , it says this:
Note that there may be multiple wifi-iface sections in this file, especially if the router is a dual band device, in which case you need to ensure that you're editing the correct section.
Unfortunately, it fails to offer any advice on which is the correct section! I suspect that almost all modern devices will be dual-band these days (late 2020) resulting in a file with ...
config wifi-iface 'default_radio0'
... and
config wifi-iface 'default_radio1'
... in it.
Which section should I use "radio0", "radio1" or both?
If I add ... option wds '1'
... to "radio0", I'm guessing only radio0 will take part in WDS?
But what happens if I add it to both "radio0" & "radio1"? Is it exclusive?
What happens if both radios are using the same SSID and only one radio has the wds=1 option added?
One way to find a possible answer it to try it? But at the head of the WiKi is a dire warning about the possibility of bricking the router if you get the instructions wrong!
I am attempting (so far without sucess) to set up two WiFi domain with WDS.
The hardware I have to hand are a pair of BT Home Hub 5A. Both have OpenWrt 19.07.4.
If I issue iw list command, I get this (abridged) output:
root@OpenWrt3:~# iw list
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* outside context of a BSS
Band 1:
Capabilities: 0x11ee
HT20/HT40
SM Power Save disabled
... output truncated here...
... is this a show-stopper (no WDS in the "Supported interface mode")?
Do you mean the WiKi I pointed to in the opening post? If so - yes. But fell at the first hurdle!
But If I were to try again, how should I implement these instructions?
Main Heading: SSH
Sub Heading: The Access Point
Once logged in, edit the /etc/config/wireless file. In the existing wifi-iface section that is being used, add a line with option wds '1'.
Note that there may be multiple wifi-iface sections in this file, especially if the router is a dual band device, in which case **you need to ensure that you're editing the correct section**.
Considering that this is my /etc/config/wireless contents:
... and why? Does this decision have any influence on the clients at the "far-end" (the ones being served by the WDS extension as they will IOT devices with only 2.4GHz radios.
I know I have asked this question before but I suspect the respondents have credited me with a greater understanding than I really possess!
Yes, I have been trying (for the last two days!). This is what I have been doing. The bullets are from the wiki..
For the wireless access point, just set the wireless mode to “Access Point (WDS)”
The BT HH5a has two radios, so I set them both. This puts the option wds '1' in the /etc/config/wireless file.
So far - so good. On we go...
On the LAN Interface, change the default IP to a different one within the target subnet and disable the DHCP server.
Again, this seemed straight forward (apart from the darn thing rolling back before I could make a connection!). My Base AP is 192.168.0.1 and my new WDS AP to 192.168.0.2.
For a wireless interface (working on the same frequency band as the Access Point), click Scan, join the previously created wireless network and when asked, set the firewall zone to lan. The wireless mode should be Client (WDS) and the Network in Interface Configuration has to be changed from wwan to lan.
My understanding (and probably wrong!), is that the new WDS AP will have one radio "looking" back for communication to/from the Base AP and the other will be the access point for the additional WDS Clients I am hoping to service. Thus, as directed, I created the Client (WDS) using the 5GHz radio. Saving the 2.4GHz radio for later (Final step in wiki)
The next three steeps: setting the DNS Forwarding, IP4 Gateway & STP in the LAN interface are again apparently quite simple steps.
At this point, I figure that I could try testing. So ...
It really can't be any easier than seeing WDS in LuCI.
All you have to do is basically set a WDS AP on the main router using ONE radio, and connect to it from the other router. All using LuCI and all as per the Wiki page.