WDS bridge on TP-Link Archer C7 V2?

Hello Folks

Following information here:
https://app.box.com/s/6hx9qhi84hr9l3kqxc3m
https://wiki.openwrt.org/doc/recipes/atheroswds

I've installed LEDE from here:


https://github.com/infinitnet/lede-ar71xx-optimized-archer-c7-v2/blob/master/lede-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade.bin
After first installing from here:
https://downloads.lede-project.org/releases/17.01.4/targets/ar71xx/generic/lede-17.01.4-ar71xx-generic-archer-c7-v2-squashfs-factory-eu.bin

And, then attempted to set up a WDS Client. I've tried to do that with a Plusnet Hub One router as WDS Master - with stock firmware. Before I'm screamed down for attempting WDS with the Hub One on stock firmware, I only attempted that after discovering my Archer C7 was running as a WDS Client when it was on stack firmware. They're both atheros devices.

The LEDE Archer C7 sees the Hub One and reports it's MAC address A4:08:F5:AE:CE:04:

root@OpenWrt0:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option channel '36'
	option hwmode '11a'
	option path 'pci0000:01/0000:01:00.0'
	option country 'GB'
	option log_level '2'
	option distance '5'
	option htmode 'VHT20'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option ssid 'OpenWrt0'
	option mode 'ap'
	option encryption 'psk2'
	option key '19ClarkeRoad'
	option wps_pushbutton '0'

config wifi-device 'radio1'
	option type 'mac80211'
	option hwmode '11g'
	option path 'platform/qca955x_wmac'
	option disabled '0'
	option channel '1'
	option log_level '2'
	option htmode 'HT20'
	option country 'GB'
	option distance '10'

config wifi-iface
	option ssid 'OpenWrt0'
	option encryption 'psk2'
	option device 'radio1'
	option mode 'sta'
	option bssid 'A4:08:F5:AE:CE:04'
	option key '19ClarkeRoad'
	option wds '1'
	option wps_pushbutton '0'
	option network 'lan'

config wifi-iface
	option device 'radio1'
	option mode 'ap'
	option ssid 'OpenWrt0'
	option network 'lan'
	option encryption 'psk2'
	option key '19ClarkeRoad'
	option wps_pushbutton '0'

root@OpenWrt0:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option channel '36'
	option hwmode '11a'
	option path 'pci0000:01/0000:01:00.0'
	option country 'GB'
	option log_level '2'
	option distance '5'
	option htmode 'VHT20'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option ssid 'OpenWrt0'
	option mode 'ap'
	option encryption 'psk2'
	option key '19ClarkeRoad'
	option wps_pushbutton '0'

config wifi-device 'radio1'
	option type 'mac80211'
	option hwmode '11g'
	option path 'platform/qca955x_wmac'
	option disabled '0'
	option channel '1'
	option log_level '2'
	option htmode 'HT20'
	option country 'GB'
	option distance '10'

config wifi-iface
	option ssid 'OpenWrt0'
	option encryption 'psk2'
	option device 'radio1'
	option mode 'sta'
	option bssid 'A4:08:F5:AE:CE:04'
	option key '19ClarkeRoad'
	option wds '1'
	option wps_pushbutton '0'
	option network 'lan'

config wifi-iface
	option device 'radio1'
	option mode 'ap'
	option ssid 'OpenWrt0'
	option network 'lan'
	option encryption 'psk2'
	option key '19ClarkeRoad'
	option wps_pushbutton '0'

root@OpenWrt0:~#

But, no packets...
Some screen shots of my Luci config, here:https://www.dropbox.com/s/wt70ok2pvyu75dy/WDSBidgeSetup.pdf?dl=0

I wonder if anyone can tell me if I've missed something here, or I should go back to the stock firmware (before getting LEDE on the Hub One - a longer term project)

Thanks
Morgan.

WDS in the terms of LEDE's /etc/config/wireless is also called 4addr mode, this is a mac80211 specific extension to support bridging two wlan bssids. This requires nl80211/ 4addr compatible drivers on all participating APs.

As long as your TP-Link Archer C7 v2 is running LEDE, it is using the mainline mac80211 based ath9k/ ath10k drivers which do support 4addr mode (WDS).

Your Plusnet Hub One however is running the OEM firmware, which is not using the linux kernel's mac80211 based ath9k/ ath10k drivers, but uses QCA's proprietary ath_pci drivers with their own BSD derived wireless stack and proprietary HAL instead - these drivers do not support 4addr mode and can't interoperate with LEDE in a WDS setup. Given that the Plusnet Hub One uses identical hardware as the BT Home Hub 5A in a different casing, it would be possible to run LEDE on your Plusnet Hub One as well, that way also using the 4addr capable ath9k/ ath10k drivers instead of the proprietary ath_pci, which would make WDS mode between your two routers possible. The BT HomeHub 5.0 Type A is a rather popular device to run LEDE (pretty much full hardware support, including the VDSL modem), but doing the initial flash requires hardware modifications (small scale SMD soldering). The initial flash is not quite trivial, but probably worth it - you can also often find these devices preflashed with LEDE for rather little money.

If the Hub One has you enter a list of MAC addresses to be WDS peers, that is the proprietary WDS mode. It is not compatible with AP(WDS) -- STA(WDS) or anything else in the open drivers.

Thanks slh & mk24

I'll get to work on the Hub One - Plusnet sent me two by mistake, so I've had one sitting on my desk waiting for surgery :slight_smile:

Out of interest - does the TP-Link stock firmware use the same propriety drives? Was that why it set up the link when I selected Client (WDS) on the TP-Link without doing anything to the Hub One? Also, interested to know how the TP-Link could see the mac address of the Hub One?

Thanks
Morgan.