- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Attribute "Class" in RADIUS accounting
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- 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
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP