[GH-ISSUE #1381] Incorrect behavior since PR#1365 was merged #422

New issue

Closed

opened 2026-02-27 14:51:43 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 14:51:43 +03:00

Owner

Originally created by @gmarcy on GitHub (Dec 24, 2023).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1381

Describe the bug

Ever since PR#1365 was merged my systems all boot into the interactive menu instead of using the boot filename returned from DHCP server. images were built w/ explicit

bootloader_tftp_enabled: false

To Reproduce
Steps to reproduce the behavior:

reboot a system using ipxe when dhcp returns a filename to use to boot. tftp-server is set to next-server here:

isset ${next-server} && isset ${proxydhcp/next-server} && goto choose-tftp || set tftp-server ${next-server} && goto load-custom-ipxe

since filename is set you always end up in tftpmenu

:load-custom-ipxe
isset ${tftp-server} && isset ${filename} && goto tftpmenu

tftpmenu never even uses filename, so will always end up here

chain --autofree tftp://${tftp-server}/menu.ipxe

Expected behavior

I expect it to use the filename I've configured dhcp to return and I expect it to use http on the server I've configured in the boot_domain rather then booting from the tftp server when I've disabled booting from tftp

Screenshots

Additional context

Originally created by @gmarcy on GitHub (Dec 24, 2023). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1381 **Describe the bug**  Ever since [PR#1365](https://github.com/netbootxyz/netboot.xyz/pull/1365) was merged my systems all boot into the interactive menu instead of using the boot filename returned from DHCP server. images were built w/ explicit ``` bootloader_tftp_enabled: false ``` **To Reproduce** Steps to reproduce the behavior: 1. reboot a system using ipxe when dhcp returns a filename to use to boot. tftp-server is set to next-server here: ``` isset ${next-server} && isset ${proxydhcp/next-server} && goto choose-tftp || set tftp-server ${next-server} && goto load-custom-ipxe ``` 2. since filename is set you always end up in tftpmenu ``` :load-custom-ipxe isset ${tftp-server} && isset ${filename} && goto tftpmenu ``` 3. tftpmenu never even uses filename, so will always end up here ``` chain --autofree tftp://${tftp-server}/menu.ipxe ``` **Expected behavior**  I expect it to use the filename I've configured dhcp to return and I expect it to use http on the server I've configured in the boot_domain rather then booting from the tftp server when I've disabled booting from tftp **Screenshots**  **Additional context**

kerem

2026-02-27 14:51:43 +03:00

closed this issue
added the
bug
label

kerem referenced this issue

2026-03-01 18:35:32 +03:00

[GH-ISSUE #422] Add support for boot loader customization #1696

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#422

No description provided.

Rows
Columns