The ONLY syntax accepted is radius<id>-<vendor> for example: 3com attribute 3Com-Product-ID should be coded as radius255-43 Where 255 is the attribute number from the 3Com dictionary and 43 is the VENDOR id of 3Com. Standard attributes should be coded with VENDOR 0. For example standard Connect-Info...

Yes I was also very surprised to learn that LLDP is not supported....

So Mikrotik, Please implement it!
LLDP +1 !

Is is raining/foggy in the area? WiFi 2.4Ghz is attenuated by moisture in the air. 5Ghz Wifi is less prone to this.

try to use directional antennas: http://www.radiolabs.com/Articles/wifi-antenna.html This will dim the other AP's in the area.

I would run Wireless-> Frequency usage, and choose a channel with low usage if at all possible. In some areas there are just too many AP's so WiFi gets quite useless. Cables are always better!

Is your problem poor WiFi reception?
Are there 20 accesspoints in the neighbourhood?

I am trying to bridge untagged (native vlan) traffic and tagged traffic from a Ubiqity WiFi radio. The untagged traffic is for managing the radio, the tagged traffic contains user-data from the SSIDs on the radio. I have the vlan defined on ethernet-2. Then I have two bridges: bridge-hs-mngt and bri...