- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Attribute "Class" in RADIUS accounting
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2016 05:31 AM
09-15-2016 05:31 AM
Attribute "Class" in RADIUS accounting
I have controller MSM760 (6.6.0.0-22530) and AP MSM410/MSM430.
I want to use "RADIUS accounting".
I need to attribute "Class" contains the necessary information to me, such as string "tac".
The manual says:
Class (string) As defined in RFC 2865. Multiple instances are supported.
The RFC 2865 says:
5.25. Class Description This Attribute is available to be sent by the server to the client in an Access-Accept and SHOULD be sent unmodified by the client to the accounting server as part of the Accounting-Request packet if accounting is supported. The client MUST NOT interpret the attribute locally.
But the default attribute "Class" already contains data unintelligible «70:0d:07:9a:00:00:01:37:00:01:02:00:0a:00:09:21:00:00:00:00:61:0b:6c:5f:0e:7b:db:a9:01:d2:03:5e:46:1e:de:10:00:00:00:00:00:01:dc:83»,
and if I add the attribute "Class" = "tac" on the RADIUS server, I still do not see this "Class" = "tac" in the accounting information.
Why attribute "Class" already contains information and why not add my information?
link captured packets