Project

General

Profile

Actions

Bug #15518

closed

Kea does not send configured TFTP server name

Added by Martin Hengesbach 7 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Category:
DHCP (IPv4)
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
2.7.2
Affected Architecture:

Description

I've a working environment with ISC dhcp server booting a raspberry pi over network. When switching to KEA dhcp the "DHCP Offer" don't contain the TFTP server name. Switching back to ISC dhcp solves the problem. I tried also to apply the soloutin from https://redmine.pfsense.org/issues/15032 but this didn't helped.

Attached the tcpdump with ISC and KEA to show the difference

The file ExtractFrom_kea-dhcp4.conf contains an enxcerpt from my kea config, the "tftp-server-name" is there.


Files

KEA DHCP Offer.png (85.2 KB) KEA DHCP Offer.png TCPdump with KEA Martin Hengesbach, 05/25/2024 05:15 AM
ISC DHCP Offer.png (82.8 KB) ISC DHCP Offer.png TCPDump with ISC Martin Hengesbach, 05/25/2024 05:15 AM
ExtractFrom_kea-dhcp4.conf (1.31 KB) ExtractFrom_kea-dhcp4.conf Excerpt from kea config Martin Hengesbach, 05/25/2024 05:23 AM
clipboard-202405251029-bx7yu.png (36.5 KB) clipboard-202405251029-bx7yu.png Lev Prokofev, 05/25/2024 06:28 AM
Actions #1

Updated by Lev Prokofev 7 months ago

I can confirm this behavior on 24.03, I was able to fix it by adding the string "code": 66 in the config

Example:

  "pools": [
                    {
                        "pool": "192.168.200.30 - 192.168.200.100",
                        "client-class": "pool_opt9_0",
                        "option-data": [
                            {
                                "name": "domain-name-servers",
                                "data": "192.168.200.1, 1.1.1.1, 8.8.8.8" 
                            },
                            {
                                "code": 66,
                                "name": "tftp-server-name",
                                "data": "192.168.200.200" 
                            },

Actions #2

Updated by Danilo Zrenjanin 7 months ago

  • Status changed from New to Confirmed

I can confirm this behavior on 24.03. The Lev's workaround works.

Actions #3

Updated by Christian McDonald 6 months ago

  • Assignee set to Christian McDonald

This is strange because as per Kea documentation:

Note that either name or code is required; there is no need to specify both...

https://kea.readthedocs.io/en/kea-2.6.0/arm/dhcp4-srv.html#standard-dhcpv4-options

Actions #4

Updated by A Schnee 6 months ago

It seems that I experienced the same issue: wiht kea DCHP cannot netboot raspberry pi. Switched back to ISC DHCP for now.

Actions #5

Updated by Christian McDonald 6 months ago

  • Target version set to CE-Next
  • Plus Target Version set to 24.08
Actions #6

Updated by Christian McDonald 2 months ago

  • Status changed from Confirmed to Feedback
Actions #7

Updated by Jim Pingle 2 months ago

  • Plus Target Version changed from 24.08 to 24.11
Actions #8

Updated by Jim Pingle 2 months ago

  • Subject changed from KEA DHCP sends no tftp server name to Kea does not send configured TFTP server name
Actions #9

Updated by Lev Prokofev 2 months ago

  • Status changed from Feedback to Resolved

The issue appears to be fixed in 24.11. I successfully boot devices using legacy and EFI PXE. I marked it as resolved.

Tested on

24.11-ALPHA (amd64)
built on Wed Oct 16 9:00:00 MSK 2024
FreeBSD 15.0-CURRENT
Actions

Also available in: Atom PDF