Update again:
Problem fixed, but no clue how or why:
My employer took a turn fiddling with settings, deleting and re-adding settings, and it just started working..
So, in answer to my own question, here are my notes:
By Jesse.
For two RB411 units running firmware 3.10, license level 3, in a point to point transparent ethernet bridge.
Yes, this works.
The client must be in "station wds" mode, on the "Wireless" tab for the wlan interface.
WDS in the WDS tab does not need to be enabled, nor does the default bridge need to be set in the WDS tab.
The AP must be set to “Bridge” mode in the wireless tab, and WDS (in the WDS tab) must be set to “Dynamic,”
and “Default bridge” must be set to the name of the bridging device (for example, “bridge1”)
Note that with the AP in "Bridge" mode and the WDS disabled, and the client in "Station" mode also with WDS disabled, the cards do
happily associate, but no traffic is passed between them.
\
\
If AP is "Bridge without WDS" and the Client is "station wds" then the client will not associate.
If AP is in "Bridge with WDS=Dynamic," then client can associate either as "station" or "station wds,"
but the bridge only passes traffic if the station is set as "station wds."
It works to have one IP on the bridge interface (which does not have to be named bridge-wds), and no IP on either wlan. or either1.
But an IP on all 3 is fine to have, and the unit can be connected to via any of the IPS except perhaps the one on the wlan1
interface.
In any case, both the wlan and ethernet interfaces must be slaves to (assigned to/claimed by) the bridge.
Also note that the bridging engine sometimes takes up to 30 seconds to learn who's on what port before it begins passing traffic, so
remember to be patient.
Also note that sometimes when changing IPs, the unit becomes unreachable even though all the settings are perfect. A reboot should fix it.
~~~~~~~
So here's the recipe for a ethernet wireless point to point transparent bridge using two RB411 (or probably other) License level 3, OS version 3.10 (and probably others.):
1: Set client AND AP to have wlan and ether to be assigned to their bridge device,which you will have to create.
2: Set the AP to mode=bridge, and turn WDS to Dynamic, and set WDS "Default Bridge" to the bridge device.
3: Set the Client to mode="station wds".
If you want to be able to manage it with IP tools (like telnet, ssh, winbox, webbox) you'll want to add IPs to the bridge interfaces and/or the ether interfaces. You can also add an IP to the wlan interfaces, but I'm not too sure why you'd need to.
Also, of course, the bridge cannot work unless the wireless cards associate. To do that, they must have the same ssid and encryption settings and everything.
Of course my original problem was that the cards would not associate at all, even though the client side could see the AP side in a "SCAN" - but that magically fixed itself.
Sincerely,
Jesse