Some Android smartphones send only accounting request

[Nick Lowe]

No, it is not only relevant where you have more than one AP.

That attribute is often needed if roaming from one BSS to another BSS takes
place or where a new session is created based on cached auth state for the
same BSS.
The sessions are related to the same EAP authentication, yet are accounted
for independently, and therefore need to be linked - that is done by an
Acct-Multi-Session-Id attribute.

At the time that that RFC was written, APs typically did not include more
than one radio or offer support for VAPs.

If your AP is accounting for a new session but where it is related to a
previous one via the same auth, it must include an Acct-Multi-Session-Id
for you to be able to correlate these.

That sounds like a Meraki limitation/bug if they are not generating and
including this attribute and you should report it to the vendor.

Regards,

Nick

On Wed, Aug 19, 2015 at 3:09 PM, Riccardo locatelli <
riccardo.locatelli at netweek.it> wrote:

> no, in accountign quest i see only Acct-Session-Id... if I understand this
> need if you use more ap, in this moment i use only 1 ap.
>
> 2015-08-19 15:35 GMT+02:00 Nick Lowe <nick.lowe at gmail.com>:
>
> > Is your Meraki AP sending an Acct-Multi-Session-Id attribute in its
> > Accounting-Request packets?
> >
> > See: https://tools.ietf.org/html/rfc3580#section-2.2
> >
> > Regards,
> >
> > Nick
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
> >
>
>
>
> --
> Riccardo Locatelli
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>