Opened 7 years ago

Last modified 4 years ago

#2890 new task

Resolve disparaties between ISC_DHCP and b10-dhcp4 in packet handling

Reported by: tmark Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: dhcp4 Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by tmark)

During v4.robustness test creation (Trac# 2600) disparities between how ISC_DHCP and b10-dhcp4 respond to certain packet content came to light. For example:

  1. In response to a DHCPREQUEST, sent to a server at 172.16.1.1, with giaddr=172.16.1.4, no ciaddr, and request address of 186.16.1.18 ISC_DHCP sends a NAK, while b10-dhcp4 sends an OFFER.
  1. In response to a DHCPREQUEST, sent to a server at 172.16.1.1, with no giaddr of 172.16.1.4, no ciaddr, and no request address, ISC_DHCP finds no matching lease and does not respond, b10-dhcp4 responds with an OFFER.
  1. In response to a DHCPDISCOVER with relay agent option set o "blah blah blah", ISC_DHCP detects invalid packet via parsing error, while b10-dhcp4 extends an offer.

Trac# 2889 was created to codify requirements for RFC2131, Section 4.3. In conjunction with that effort identification reconciliation of differing behavior between of ISC_DHCP and b10-dhcp4 to various packet content should be conducted.

This should include codification of what is and is not a valid inbound packet.

Subtickets

Change History (2)

comment:1 Changed 7 years ago by tmark

  • Description modified (diff)

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.