Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 509
    • Issues 509
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 49
    • Merge requests 49
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • #663

Closed
Open
Created Jun 11, 2019 by Andrei Pavel@andrei🐧Maintainer

Wrong client port in offer?!

perfdhcp -D 1024 -d 1024 -d 1024 -f 16 -L 12345 -l ens4 -n 1024 -n 1024 -r 16 -4 -R 4294967295 -W 0

on a back-to-back pair of interfaces with kea-dhcp4, no relay involved. Notice the non-default port -L 12345. perfdhcp gets no response whatsoever. GDBed into the kea-dhcp4, receives the query with remote_port_ 12345, but it populates the response's remote_port_ with 68.

The -P parameter on kea-dhcp4's side could be used here, but what about a production situation?

I feel like I'm in the wrong cuz this would be detected quickly, but maybe nobody uses non-default ports for their clients and it also feels like perfdhcp should get it's response. Help?

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