starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-25 07:05:56 +03:00

[GH-ISSUE #952] Add support for proxy DHCP #1792

New issue

Closed

opened 2026-03-01 18:36:25 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 18:36:25 +03:00

Owner

Originally created by @notepass on GitHub (Aug 5, 2021).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/952

Is your feature request related to a problem? Please describe.
While setting up a netboot server, I had to use a DHCP proxy to inject the boot server IP into the network. This had to be done, as my DHCP server has no support for setting the "next-server" option. When now booting the netboot.xyz instance, it tried to access the .ipxe files not from my tftp server, but from the server provided by my root DHCP. As there was no tftp server running, all requests timed out (although the normal menu showed up). To reproduce this, the docker container in the repo "samdbmg/dhcp-netboot.xyz" can be used, as that starts up a dnsmasq dhcp proxy.

Describe the solution you'd like
When a DHCP proxy exist, netboot.xyz should detect it and honor it in some way. It is a bit hard for me to say in which way would be the best, but I would think of something like this:

Check if next-server is set
- If no, check if proxydhcp/next-server is set. If yes, use that to access .ipxe files
- If yes, check if proxydhcp/next-server is set. If yes, show a prompt telling the user that the proxy-provided server is used instead of the server provided by to root dhcp.
  - But also give the user a prompt to override this (e.g. by pressing e or something)
  - Additionally, a ipxe file could be accessed on the root dhcp provided server (e.g. proxy-dhcp-vars.ipxe) which could set default vars to override any of this behaviour

Describe alternatives you've considered
N/A

Additional context
I'm currently trying to implement this in a fork. If you would consider adding this feature, I might be able to implement it or submit a PR for it.

Originally created by @notepass on GitHub (Aug 5, 2021). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/952 **Is your feature request related to a problem? Please describe.** While setting up a netboot server, I had to use a DHCP proxy to inject the boot server IP into the network. This had to be done, as my DHCP server has no support for setting the "next-server" option. When now booting the netboot.xyz instance, it tried to access the .ipxe files not from my tftp server, but from the server provided by my root DHCP. As there was no tftp server running, all requests timed out (although the normal menu showed up). To reproduce this, the docker container in the repo "samdbmg/dhcp-netboot.xyz" can be used, as that starts up a dnsmasq dhcp proxy. **Describe the solution you'd like** When a DHCP proxy exist, netboot.xyz should detect it and honor it in some way. It is a bit hard for me to say in which way would be the best, but I would think of something like this: * Check if next-server is set * If no, check if proxydhcp/next-server is set. If yes, use that to access .ipxe files * If yes, check if proxydhcp/next-server is set. If yes, show a prompt telling the user that the proxy-provided server is used instead of the server provided by to root dhcp. * But also give the user a prompt to override this (e.g. by pressing e or something) * Additionally, a ipxe file could be accessed on the root dhcp provided server (e.g. proxy-dhcp-vars.ipxe) which could set default vars to override any of this behaviour **Describe alternatives you've considered** N/A **Additional context** I'm currently trying to implement this in a fork. If you would consider adding this feature, I might be able to implement it or submit a PR for it.

kerem

2026-03-01 18:36:25 +03:00

closed this issue
added the
no-issue-activity

work-in-progress
labels

kerem commented

2026-03-01 18:36:26 +03:00

Author

Owner

@notepass commented on GitHub (Aug 5, 2021):

Created PR #953 to implement this feature

@notepass commented on GitHub (Aug 5, 2021): Created PR #953 to implement this feature

kerem commented

2026-03-01 18:36:26 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 5, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 5, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kerem commented

2026-03-01 18:36:26 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 6, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Oct 6, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

kerem commented

2026-03-01 18:36:26 +03:00

Author

Owner

@antonym commented on GitHub (Oct 24, 2021):

Looks to be functioning now with a few changes. Going to close this out but feel free to test with the development endpoint and binaries:

https://s3.amazonaws.com/dev.boot.netboot.xyz/cf44496e311bf2bf597856b22a2b1368d961ef76/index.html

@antonym commented on GitHub (Oct 24, 2021): Looks to be functioning now with a few changes. Going to close this out but feel free to test with the development endpoint and binaries: https://s3.amazonaws.com/dev.boot.netboot.xyz/cf44496e311bf2bf597856b22a2b1368d961ef76/index.html

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#1792

No description provided.

Rows
Columns