Traffic accounting about uspot HOT 4 OPEN

I wanted to also ask this.

Looking at the source code it looks like a lot of the work has already been done to support accounting interim/stop packets, so hopefully it isn't too much hassle to add this data to the Acct-Input-Octets and Acct-Output-Octets attributes in?

This is the number one reason why I can't switch over from coovachilli today, else I would be adopting uspot straight away as I love it.

from uspot.

Traffic accounting is non-trivial to implement correctly. It's high priority on my todo list though, so it'll happen "as soon as possible".

from uspot.

Traffic accounting is non-trivial to implement correctly. It's high priority on my todo list though, so it'll happen "as soon as possible".

Thank you. Is it likely to be in the next few months, or sometime this year? Also, I am happy to help beta test. I have numerous deployments and lab facilities.

Thanks

from uspot.

@f00b4r0 A related question on this...

The code indicates data usage limits can be set via ChilliSpot-Max-Total-Octets - is this implemented considering there is no traffic accounting at present?

Thanks

from uspot.