2015-06-05 0:59 GMT+08:00 d tbsky <tbskyd@gmail.com>:
Hi Alan:
2015-06-05 0:47 GMT+08:00 d tbsky <tbskyd@gmail.com>:
Hi Alan:
2015-06-04 21:17 GMT+08:00 Alan DeKok <aland@deployingradius.com>:
On Jun 4, 2015, at 7:02 AM, d tbsky <tbskyd@gmail.com> wrote:
3. use my notebook to login AP. fr can not create a new accounting entry, it seems "Acct-Session-Id" will be reused
Your AP is broken. Throw it in the garbage, and buy one that follows the RADIUS standards. RFC 2866 Section 5.5 says that the Acct-Session-Id is unique to each session.
my test AP is running openwrt + hostpad. I think the Acct-Session-Id is unique for every live session. but after reboot the Acct-Session-Id will be re-used again. I check RFC 2866, but it didn't say Acct-Session-id should be unique after reboot. but maybe the AP should make it unique for every session ever connected? I am confused about this..
just find out the latest hostapd 2.4 changelog (https://w1.fi/cgit/hostap/plain/hostapd/ChangeLog):
fixed Accounting-Request to not include duplicated Acct-Session-Id
No.. check the detail of the commit (http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=commit;h=aff039fada2f10b095631...) the fix is not related to unique Acct-Session-Id.. so still confused about if the id should be unique after reboot..