DHCP server not working for iPXE

[excessive]

The switch is BlackDiamond X8.
I’ve set dhcp server for our lab VLAN that I’m using for testing. The pool range and everything else works as intended.
I’ve configured options 66 and 67 to FOG server machine and that’s where it breaks. I’m getting:

Filename: undionly.kpxe
Could not start download: Operation not supported (http://ipxe.org/3c092003)

I can confirm that when using separate isc-dhcp server there’s no problem. But I’d like to utilize our switch.

Here’s snippet of my configuration:

VLAN "XXX_TEST":
    DHCP Address Range   : 192.168.xx.xx->192.168.xx.xx
    Netlogin Lease Timer : Not configured (Default = 10 seconds)
    DHCP Lease Timer     : 86400 seconds
    Default Gateway      : 192.168.xx.xx
    Primary DNS Server   : xx.xx.xx.xx
    DHCP Option Code  66 : ipaddress 192.168.xx.xx
    DHCP Option Code  67 : string "undionly.kpxe"
    Ports DHCP Enabled   : 1:21

[StephanH]

Hello, yes that’s the point. How does the according config line looks like in your switch?

[excessive]

Option: (66) TFTP Server Name
    Length: 4
    TFTP Server Name: ���3


Option: (67) Bootfile name
    Length: 13
    Bootfile name: undionly.kpxe

Seems like option 66 is in wrong format, or for some reason looks unreadable.

67 seems to be correct.

[StephanH]

Greate, what we see is that option 66 and option 67 are present, that’s good. Normaly you should be able to expant the single option by clicking in wireshark. Can you do this for Option 66 ind 67? Then we will see what is the content of the options.

[excessive]

Hi Stephan. Thank you for your time.
This morning I mirrored the port to the port of my Wireshark computer. Now I got  ONLY Offer and ACK frames. Here they are:

Frame 124877: 337 bytes on wire (2696 bits), 337 bytes captured (2696 bits) on interface \Device\NPF_{4C63F991-A548-48B3-A772-5278B943AE7F}, id 0
Ethernet II, Src: ExtremeN_9b:8e:d0 (00:04:96:9b:8e:d0), Dst: 82:5d:c6:8a:7e:48 (82:5d:c6:8a:7e:48)
Internet Protocol Version 4, Src: 192.168.230.253, Dst: 192.168.230.200
User Datagram Protocol, Src Port: 67, Dst Port: 68
Dynamic Host Configuration Protocol (Offer)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x1d398b73
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0
    Your (client) IP address: 192.168.230.200
    Next server IP address: 0.0.0.0
    Relay agent IP address: 0.0.0.0
    Client MAC address: 82:5d:c6:8a:7e:48 (82:5d:c6:8a:7e:48)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (51) IP Address Lease Time
    Option: (53) DHCP Message Type (Offer)
    Option: (1) Subnet Mask (255.255.255.0)
    Option: (54) DHCP Server Identifier (192.168.230.253)
    Option: (3) Router
    Option: (6) Domain Name Server
    Option: (66) TFTP Server Name
    Option: (67) Bootfile name
    Option: (255) End

Frame 137003: 337 bytes on wire (2696 bits), 337 bytes captured (2696 bits) on interface \Device\NPF_{4C63F991-A548-48B3-A772-5278B943AE7F}, id 0
Ethernet II, Src: ExtremeN_9b:8e:d0 (00:04:96:9b:8e:d0), Dst: 82:5d:c6:8a:7e:48 (82:5d:c6:8a:7e:48)
Internet Protocol Version 4, Src: 192.168.230.253, Dst: 192.168.230.200
User Datagram Protocol, Src Port: 67, Dst Port: 68
Dynamic Host Configuration Protocol (ACK)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x1d398b73
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0
    Your (client) IP address: 192.168.230.200
    Next server IP address: 0.0.0.0
    Relay agent IP address: 0.0.0.0
    Client MAC address: 82:5d:c6:8a:7e:48 (82:5d:c6:8a:7e:48)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (51) IP Address Lease Time
    Option: (53) DHCP Message Type (ACK)
    Option: (1) Subnet Mask (255.255.255.0)
    Option: (54) DHCP Server Identifier (192.168.230.253)
    Option: (3) Router
    Option: (6) Domain Name Server
    Option: (66) TFTP Server Name
    Option: (67) Bootfile name
    Option: (255) End

[StephanH]

In that way you are tracing you will see only broadcasts. The Offer can be a unicast and the ACK will be a unicast and a unicast will not reach you station. Therefore you have to create an mirror port or you can trace directly on the device getting the ip address.