Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#4333 closed defect (complete)

Cannot find answer for helper-address from cisco

Reported by: duanezi Owned by: duanezi
Priority: medium Milestone: Kea1.1
Component: Unclassified Version: 1.0.0
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 4 Internal?: no

Description (last modified by duanezi)

I am new to Kea and thus far I really like what you guys are doing. Unfortunately I cannot find the answer to ip helper-address issues. I have a pool defined

"subnet4": [



"relay": { "ip-address": "x.x.43.65" },
"subnet": "",
"pools": [ { "pool": " -" }]



My requests are coming in and I do have my interfaces mapped properly but I get the error message.

2016-03-16 23:38:02.682 ERROR [kea-dhcp4.bad-packets/6830] DHCP4_PACKET_NAK_0001 [hwtype=1 0a:00:3e:26:d0:08], cid=[no info], tid=0x2233450a: failed to select a subnet for incoming packet, src x.x.46.65, type DHCPDISCOVER

I'm running 1.0.0.

Any help in this would be great.



Change History (4)

comment:1 Changed 4 years ago by sar

The ip-address in the relay statement is compared against the giaddr field the relay puts into the DHCP message.

The log messages indicate that the from address of the relayed packet was the one you specified but this may not be the address the relay is using for the giaddr field for this subnet. You should check what giaddr is, either by looking on the relay or by using a packet capture tool.

comment:2 Changed 4 years ago by duanezi

  • Description modified (diff)
  • Owner set to duanezi
  • Status changed from new to accepted

comment:3 Changed 4 years ago by duanezi

  • Resolution set to complete
  • Status changed from accepted to closed

comment:4 Changed 4 years ago by hschempf

  • Milestone changed from Kea-proposed to Kea1.1
  • Total Hours changed from 0 to 4
Note: See TracTickets for help on using tickets.