Opened 7 years ago

Last modified 4 years ago

#2985 new defect

rfc 2131 vs monitoring network interfaces

Reported by: jankowsr Owned by:
Priority: low Milestone: Outstanding Tasks
Component: dhcp4 Version:
Keywords: dhcpv4 Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Low
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


As of now kea does not monitor the state of network interfaces. It does not utilize network interfaces started after b10-dhcp4 module initialization. This means it's not quite compliant with the following part of RFC 2131:

"The 'server identifier' field is used both to identify a DHCP server
in a DHCP message and as a destination address from clients to
servers. A server with multiple network addresses MUST be prepared
to to accept any of its network addresses as identifying that server
in a DHCP message."

How to reproduce:

config add Init/components b10-dhcp4
config set Init/components/b10-dhcp4/kind dispensable
config commit

start new network interface
send DHCP discover to this new interface

Expected Result:
server should respond to DHCPDISCOVER

Actual Result:
server will discard DHCPDISCOVER


Change History (2)

comment:1 Changed 6 years ago by shane

  • Milestone changed from New Tasks to DHCP Outstanding Tasks

comment:2 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.