Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 422
    • Issues 422
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #81

Closed
Open
Opened Aug 27, 2018 by trac migrator@trac-migrateDeveloper

RADIUS hook issue? Duplicated attributes in RADIUS requests after reloading config

Itay Rozenburg reports to us:

Greetings Support

  1. I think I found a bug in the radius hook.

    When I reload the configuration via rest api, The radius requests looks weird, You can see Some of the attributes twice in each request. Access-Request (1), id: 0x54, Authenticator: **** User-Name Attribute (1), length: 20, Value: xxxyyy User-Password Attribute (2), length: 18, Value: *** User-Password Attribute (2), length: 18, Value: *** Calling-Station-Id Attribute (31), length: 19, Value: aa:bb:cc:dd:ee:ff NAS-Identifier Attribute (32), length: 5, Value: kea NAS-Identifier Attribute (32), length: 5, Value: kea Connect-Info Attribute (77), length: 41, Value: xxx Connect-Info Attribute (77), length: 41, Value: xxx NAS-Port Attribute (5), length: 6, Value: 1480 NAS-IP-Address Attribute (4), length: 6, Value: 10.1.1.1

    If I reload the process everything looks fine.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Kea1.5-final
Milestone
Kea1.5-final (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#81