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 445
    • Issues 445
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 71
    • Merge Requests 71
  • 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
  • #414

Closed
Open
Opened Jan 16, 2019 by Francis Dupont@fdupontDeveloper

Use new lease user contexts in RADIUS accounting

Migrated from https://oldkea.isc.org/ticket/5658

Current code has many potential problems and was scheduled to use use contexts from the beginning but it was postponed because user contexts in leases were implemented later:

  • save/load to a CSV file is implemented but never tested.
  • eraseCreateTimestamp() is called only when a STOP event is sent so the timestamp stays in memory without more control
  • obviously using an user-context is the right way: extent following the lease one, save in stable storage, etc.

If memory leak on RADIUS accounting experiments are not conclusive this should be tried.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Kea2.x
Milestone
Kea2.x
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#414