When using a ZoneDirector 1200 running 10.5.1.0.282 (GA Refresh 9) to control multiple R600 APs, none of the APs can connect properly as mesh nodes (MAP), even though they can all connect and function as wired root nodes (RAP). The MAP's AIR light is on but the MAP never gets usable responses via the RAP: no DHCP response, no controller response, etc. ZD shows the AP is disconnected and ping attempts across the wired/wireless boundary get no responses in either direction. Output from "show mesh" indicates valid U and D neighbor relationships and strong RSSI, yet ARP cannot complete and the MAP cannot reach the RAP, gateway, or ZD. Frames are transmitted, acknowledged, authenticated, and decrypted successfully over the air.
Diagnosis is possible using over-the-air monitoring. The packets get mangled by the R600 as it relays traffic between the wired and wireless netorks. The RAP deletes protocol-header bytes when forwarding mesh traffic across the RAP Ethernet boundary. There is a workaround possible, but it involves modifying the firmware running on the AP.
I created a support case for this behavior with more detail and a recommended fix, but I don't know if ZD will have any future releases.
I believe the bug affects these models of APs: R500, R600, R310, T300, T300e, T301n, and T301s when running these versions of ZoneDirector: 10.5.1.0.282, 10.5.1.0.279, 10.5.1.0.276
This might be the cause of the behavior described in this other post "Zonedirktor 1200 After RMA replacing, mesh ap´s no longer works" and it could be another possible reason for the KnowledgeBase article "Mesh AP unable to connect to a Root AP"
