Some Android smartphones send only accounting request

[Nick Lowe]

Hi Riccardo,

This is because roaming is taking place from one BSS to another, auth isn't
therefore happening but you will observe a Stop for the old accounted
session and a Start for the new. Consider it a useful optimisation.

You should, however, see an Acct-Multi-Session-Id to link the previous
accounting session to the new accounting session when roaming occurs.

The Acct-Session-Id changes on some APs and is constant on others.
Technically, the Acct-Session-Id is AP specific so it changing is
reasonable behaviour.

You cannot use the Class attribute to track reliably as, with some APs, the
value accounted with changes in accounting when 802.1X re-authentication
takes place.

Regards,

Nick