[Kea-users] About kea with windows pxe boot

hiplon hiplon at gmail.com
Thu Jun 27 09:09:53 UTC 2019


Hi all,
    I have an issue that I use the kea dhcp 1.5.0 (and have tried 1.4.0 and
1.1.0) to announce the windows pxeboot files to the PCs, but i seems not
work.
    I have captured the windows dhcp server and dhcpd and they give the
same capture results with kea dhcp as follows:

Kea DHCP:
        172.16.249.12.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP,
Reply, length 284, xid 0xe24864b2, Flags [Broadcast] (0x8000)
 Your-IP 172.16.249.200
 Server-IP 172.16.108.23
 Client-Ethernet-Address 00:0c:29:c5:ee:3b
 file "SMSBoot\x64\wdsmgfw.efi"[|bootp]


Zeroshell with DHCPd:
    172.16.249.13.67 > 255.255.255.255.68: [udp sum ok] BOOTP/DHCP, Reply,
length 300, xid 0x7005b1b7, Flags [Broadcast] (0x8000)
 Your-IP 172.16.249.150
 Server-IP 172.16.108.23
 Client-Ethernet-Address 00:0c:29:c5:ee:3b
 file "SMSBoot\x64\wdsmgfw.efi"[|bootp]

Windows DHCP:
    172.16.249.6.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP,
Reply, length 358, xid 0x14fe91af, Flags [none] (0x0000)
 Your-IP 172.16.249.113
 Server-IP 172.16.108.23
 Client-Ethernet-Address 00:0c:29:33:b6:7e (oui Unknown)
 file "SMSBoot\x64\wdsmgfw.efi"[|bootp]

The pxeboot with dhcpd and windows dhcp can boot into the windows
installer, but keadhcp cannot.


My configuration is as follow:

{

"Dhcp4": {

    "interfaces-config": {

        "interfaces": [ "*" ]


    },


  "control-socket": {
        "socket-type": "unix",
        "socket-name": "/tmp/kea-dhcp4-ctrl.sock"
    },


  "hooks-libraries": [
    {
        "library": "/opt/kea-1.5.0/lib/hooks/libdhcp_stat_cmds.so"
    },
    {
        "library": "/opt/kea-1.5.0/lib/hooks/libdhcp_lease_cmds.so"
    }
    ],

    "lease-database": {
    "type": "memfile",
        "name": "leases4"
    },


    "expired-leases-processing": {
        "reclaim-timer-wait-time": 30,
        "flush-reclaimed-timer-wait-time": 30,
        "hold-reclaimed-time": 10,
        "max-reclaim-leases": 10,
        "max-reclaim-time": 10,
        "unwarned-reclaim-cycles": 10
    },


    "renew-timer": 864000,
    "rebind-timer": 864000,
    "valid-lifetime": 1296000,


    "option-data": [
        {
            "name": "domain-name-servers",
            "data": "xxx"
        }


    ],



    "subnet4": [
{
            "subnet": "172.16.249.0/24",
            "next-server": "172.16.108.23",
            "boot-file-name": "SMSBoot\\x64\\wdsmgfw.efi",
            "pools": [ { "pool": "172.16.249.200 - 172.16.249.220" } ],
            "relay": {
                "ip-address": "172.16.249.1"
            },
            "renew-timer": 86400,
            "rebind-timer": 86400,
            "valid-lifetime": 129600,
            "option-data": [
                {
                    "name": "routers",
                    "data": "172.20.39.1"
                }
             ]
        }

    ]
},

// Logging configuration starts here. Kea uses different loggers to log
various
// activities. For details (e.g. names of loggers), see Chapter 18.
"Logging":
{
  "loggers": [
    {

        "name": "kea-dhcp4",
        "output_options": [
            {

                "output": "/opt/kea-1.5.0/var/log/kea-dhcp4.log"

            }
        ],

        "severity": "INFO",


        "debuglevel": 0
    }
  ]
}
}


Is someone have successfully booted a pxe with the keadhcp and figure where
is my problem?

Thank you so much!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20190627/90b97194/attachment.html>


More information about the Kea-users mailing list