So after digging a bit deeper, this IOS thing has become messier. A new Ipad "activates" by hitting the internet with web browsing, OCSP, facetime, itunes etc. With captive portal turned on, the unit can not activate as the CP never shows up. After the unit is activated (via a non CP network) and the IOS device is attached to the SSID, it immediately calls home as shown here http://erratasec.blogspot.com/2010/09/apples-secret-wispr-request.html . That then forces the user to authenticate via CP. Problem is if the unit is on a network with exchange, the preferred method is to map the ip-user via the Exchange logs which can't happen until it is on the wireless. So it looks like: A non CP zone must be propped up just for activation of the units. A rule must be set to allow the unit to "call home" in order to avoid the captive portal. I have attempted to create a rule to just allow web-browsing to the special URL with no luck. For some reason, the rule allows web traffic to different URLs as well. I hope the above helps, if anyone has an idea as for a rule to allow all users to get to www.apple.com/library/test/success.html via the following I would appreciate it. GET /library/test/success.html HTTP/1.0 Host: www.apple.com User-Agent: CaptiveNetworkSupport/1.0 wispr Connection: close Bob
... View more