I’ve setup a test site (house) with a CRS125-24G-1S-RM and 4x RB951G-2HnD’s. I’m using ROS 6.11 on all devices, and I’ve installed and configured CAPsMAN. Everything’s working, except that Apple IOS clients (iPhone/iPad) can’t stream HTML5 video (eg YouTube). I’ve tried using manager forwarding and local forwarding mode, and the problem is the same in both cases. When I configure the APs manually (using the same settings), everything works properly.
I’m really looking forward to seeing CAPsMAN developed further - I’m planning on marketing a similar system to a wide client base, and even being able to configure the SSID and WPA keys in one place will make it much more user-friendly to my end-users.
Please let me know if you require any specific information about my configuration.
No, the connection to the internet is via a Draytek Vigor 120 ADSL router configured as a half-bridge (and I’ve added the appropriate rules to clamp the MSS to the PMTU). No PPPoE or other tunnels are on the Mikrotik gear.
turnip, thank you very much for the report.
I repeated the same problem on my iphone and AP controlled by CAPSMAN. We will see what we can do about it.
Normally I’m not a “me too” guy - but the very same problem here.
8x CAP controlled via a 2011UiAS.
Additionally, our phone system’s VoIP client (Aastra AMC+ client) stopped working in our work WiFi (which isn’t that pity as the clients are rolled out for people in the field… but strange).
We also have Apple TVs in our conference rooms enabling our sales team to quickly show some decks from their iPads - which also stopped working…
Just downloaded 6.13rc5 and updated one CAP for testing.
It updates smoothly but then won’t connect to the CAPsMAN (still running 6.12).
Logs remain empty on this issue.
updated the CAPsMAN 2011 and our BaseBox2 APs to 6.13rc6 and the appropriate wireless-fp package.
What I found out:
The update took slightly longer to be installed (compared to updating 6.12rc1 to 6.12 final release).
The CAPs then smoothly connected to the CAPsMAN and reported to work (all cap interfaces were created as expected, the CAPs themselves reported to run all virtual APs configured by CAPsMAN) - but clients were unable to connect to any SSID and reported timeout issues.
Since time was short, I had to downgrade to 6.12 instantly.
Will keep you updated.
Aastra rolled out a client update last week. The actual client version 4.2, build 3391 now also works in the CAPSMANaged Wireless.
As posted before, iOS devices are now able to sync their screens with the ATV in Version 6.12.
On our last bigger meeting this week we noticed that OS X devices (in this case some MacBook Airs and Pros, running either Mountain Lion or Mavericks) see the ATV again but screen sync fails.
