I have been trying to create a client bridge using MT, not a client router, and have been finding some strange behavior.
Paired with an off the shelf Linksys, Engenius, Netgear AP or a Linux box with Madwifi, I have built a client which uses Station-WDS mode:
Configuration details are:
CM9 radio module
MT 2.9.30
Station-WDS mode
Static WDS with MAC of AP
Bridge with wlan1, wds1, ether1
DHCP client on bridge1
PC hanging off ether1
Starting configuration yields no link. Station does not register with AP and no WDS link exists.
Then I disable WDS and change to station mode. Try to reconnect and the link is good and I get a DHCP address. Station registers with AP.
Then, without powering anything off, I switch back to original Station-WDS and the link works and we get bridging from the PC, so it appears that WDS works.
Everything behaves almost identically with WDS-Slave mode.
Then if I power reset the AP and the Client bridge and nothing works again until I change mode to station, associate and then change mode back.
Appears that this is consistent behavior with MT AP, Madwifi AP, Linksys AP, Netgear AP or Linux Madwifi AP.
It appears that WDS-Slave and Station-WDS modes do not create proper associations with APs, and therefore proper registration does not occur. I would expect this with WDS-Slave, as it is using WDS and would not make a station association. But shouldn't Station-WDS mode associate properly and create AP registration, regardless of whether WDS exists or not?
Has anyone successfully created a working Client Bridge using Station-WDS mode? In particular one that will keep working through power cycles of AP and Client. Shouldn't Station association be created regardless of WDS status when running Station-WDS mode?