[LEDE-DEV] wds link problem

[xinglp]

2016-08-26 12:25 GMT+08:00 J Mo <jmomo at jmomo.net>:
>
> 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.
The TP-Link routers that I tested use vxworks as OS.
>
> 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.
When then bridge to another router with different chip, the use 3-address mode,
which is working as using relayd, see
https://wiki.openwrt.org/doc/recipes/relayclient
>
> 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

Sorry, I forgot to reply to all.