Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 504
    • Issues 504
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 53
    • Merge requests 53
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #167
Closed (moved) (moved)
Open
Created Oct 15, 2018 by Vicky Risk@vickyDeveloper

Log client fingerprinting data

Identifying client device types via 'fingerprinting' is a common feature of dhcp mgmt utilities. Some users who want to do this themselves are asking where they can get the raw data from Kea. They could then use one of the open source databases such as https://fingerbank.org to determine via post processing what device type the client most likely is.

Can we log the order in which the client requests options as well as the vendor ID for use by a fingerprinting service? (e.g. options 55 and 60 from the REQUEST for DHCPv4)

This could be added to the existing forensic log hook, or we could create another hook.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking