With CAPsMAN, is the Acct-Multi-Session-Id attribute included properly in the RADIUS accounting that is performed by an access point so that there is a unique and constant session id across roams?
http://tools.ietf.org/html/rfc3580#section-2.2
Thanks,
Nick