Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 362
    • Issues 362
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 54
    • Merge Requests 54
  • Packages
    • Packages
    • Container Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #414

Closed
Open
Opened Jan 16, 2019 by Francis Dupont@fdupont
  • Report abuse
  • New issue
Report abuse New issue

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.

Assignee
Assign to
Kea1.7-backlog
Milestone
Kea1.7-backlog
Assign milestone
Time tracking
None
Due date
None
3
Labels
premium radius removal-candidate
Assign labels
  • View project labels
Reference: isc-projects/kea#414