Hi

I am mentioned in that ticket you linked. I've seen similar problems, but I'm not positive that my situation wasn't just a hardware failure. I will get in contact with that tribut person and work with him. Thanks for bringing this to my attention.

Anyway, your problem is different. TP-Link uses proprietary closed-source drivers. It's probably not even using hostapd or iw. It probably requires something proprietary to make it work. It would not surprise me if they had purposefully disabled non-TP-Link bridge clients.

This sounds like a TP-Link problem. There is likely nothing you can do about it (except to use LEDE/OpenWRT instead).

Most different closed-source wireless implementations won't bridge with each other. I don't even think 4-address bridging is a de-facto standard yet, though it's getting there.

I think you are out of luck and will not be able to fix this.

As a tangential gripe, I don't like the term "WDS". I suggest "wireless bridging" or "802.11 bridging" instead. "WDS" as a term should be depreciated. WDS doesn't mean wireless bridging and wireless bridging doesn't mean WDS. Reference: http://www.ieee802.org/1/files/public/802_architecture_group/802-11/4-address-format.doc



On 08/25/2016 08:44 PM, xinglp wrote:
With below configuration, I can connect to another router with lede
firmware, but can't connect to a router with tplink firmware.
config wifi-iface 'foo'
     option wds '1'
     option mode 'sta'
     ..

I can see it connect to tplink router and disconnect, and repeat again
and again.
The only usefull log is below:
wlan0: deauthenticating from <MAC> by local choice (Reason: 3=DEAUTH_LEAVING)

tplink router can connect to another tplink router with WDS and 4 addr
mode. I can see the log;
WDS detected RootAP supported 4-addr.

There's also a openning ticket:
https://dev.openwrt.org/ticket/20604

_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Reply via email to