The kea server and this client are both on the same subnet.
dhcp-socket-type is set to "raw".
On 2/26/22 08:02, Peter Davies wrote:
Hi Stephen,
This client appears to be directly connected with the server’s
eth0 interface.
Is 192.168.100.100 an appropriate address for this interface and is
dhcp-socket-type “raw”?
Kind Regard Peter
*From: *Stephen Berg, Code 7309 via Kea-users
<mailto:[email protected]>
*Sent: *Saturday, 26 February 2022 14.21
*To: *[email protected]
*Subject: *Re: [Kea-users] KEA and pxeboot
Can someone weigh in on why this host reservation is not working? Basic
dhcp works but when I add the next-server and boot-file-name to pxeboot
it fails. I get the two errors in the log that I'm running in debug
level currently.
{
"ip-address": "192.168.100.100",
"hostname": "server1",
"hw-address": "aa:bb:cc:dd:ee:ff",
"next-server": "192.168.100.1",
"boot-file-name": "pxelinux.0"
},
2022-02-26 07:09:26.875 DEBUG [kea-dhcp4.packets/13158.140019375193408]
DHCP4_SUBNET_SELECTION_FAILED [hwtype=1 aa:bb:cc:dd:ee:ff],
cid=[01:aa:bb:cc:dd:ee:ff], tid=0x396c44b0: failed to select subnet for
the client
2022-02-26 07:09:26.875 DEBUG
[kea-dhcp4.bad-packets/13158.140019375193408] DHCP4_PACKET_DROP_0002
[hwtype=1 aa:bb:cc:dd:ee:ff], cid=[01:aa:bb:cc:dd:ee:ff],
tid=0x396c44b0, from interface eth0: no suitable subnet configured for a
direct client
The client system never gets an IP and of course never starts into the
pxeboot process.
On 2/23/2022 9:17 AM, Stephen Berg, Code 7309 via Kea-users wrote:
> Where can I find documentation on setting up pxebooting to do linux
> installs? I'm running kea-1.8.0-2 on Rocky Linux 8.5. I want to be
> able to pxeboot different OS's like centos 7.x, rocky 8.x and future
> releases. The tftp-server is installed and setup, syslinux packages
> are installed. I've got just a couple clients defined in dhcp as
> reserved leases and added next-server and filename options for one but
> when I boot the network from that client it never seems to get to the
> pxelinux.0 or the defined kernel in the "pxelinux.cfg/01-macaddress"
> file.
>
> I figure I'm probably missing some setup in the kea-dhcp4.conf file
> but can't find what the missing parts might be.
>
> My old setup is centos 6, dhcp-4.1.1. I'd add the next-server and
> filename lines for a particular host reservation then use pxeboot to
> setup the pxelinux.cfg file and that would have kernel parameters to
> boot the installer and read a kickstart file. Right now I can get the
> new system to boot from the network, it gets an IP from kea but then
> fails to find the tftp file to boot from.
>
>
--
Stephen Berg, IT Specialist, Ocean Sciences Division, Code 7309
Naval Research Laboratory
W: (228) 688-5738
DSN: (312) 823-5738
C: (228) 365-0162
Email: [email protected] <- (Preferred contact)
Flank Speed: [email protected]
--
Stephen Berg, IT Specialist, Ocean Sciences Division, Code 7309
Naval Research Laboratory
[email protected] <- (Preferred contact)
W: (228) 688-5738
DSN: (312) 823-5738
C: (228) 365-0162
--
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
