I have about eleventy-billion WET200 wireless bridges out at client sites, and I am having no end of compatibility issues.
With WET200 trying to talk to a ValuePoint MultiAP 700 or 770, I cannot associate at all, link quality stays at 0%. We had to buy another bridge solution for that site.
With WET200 trying to talk to a Routerboard AP, I associate just fine. Link quality is normal, both ends show I'm connected. However, I can't pass any non-broadcast traffic across the wireless link. I can sniff the network on the bridge, and I see STP from the remote end, I see Windows networking chatter, but I can't ping/SSH/HTTP or anything across that link. This problem is bidirectional. If I drop the network from WPA2/AES PSK to WPA1/TKIP PSK, it suddenly works just fine, except I get no DHCP leases across the link.
Is this just the most incompatible product ever? Or do you folks know some magical incantations that I do not? In both environments, multiple laptops with multiple radios can associate and pass traffic just fine. With the WET200, the *WET200* is the common denominator, and it just doesn't work.
I have tried firmware 1.0.9 and the latest (I believe 1.0.13 as of July 2009).
Thanks VERY MUCH for any help... If I cannot find a solution, I'm going to have to find a different bridge to roll out to clients.