mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-26 07:35:57 +03:00
[GH-ISSUE #736] Next-server constantly overwritten to router IP after configuring net0 through dnsmasq with ProxyDHCP configuration #213
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#213
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jarylc on GitHub (Oct 29, 2020).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/736
To Reproduce
172.17.0.2instead of172.17.0.11)Additional context
Expected behavior
Next-server IP address should be pointed to my virtual machine hosting Netboot.XYZ at
172.17.0.11instead of my router at172.17.0.2@antonym commented on GitHub (Oct 29, 2020):
Try adding a dhcp-option?
dhcp-option=66,"x.x.x.x"
https://forums.fogproject.org/topic/7723/pxe-ipxe-dnsmasq-next-server-undionly-config-tip-s
@jarylc commented on GitHub (Oct 29, 2020):
I've tried that along with
dhcp-option-force, it doesn't seem to be working.Is there a way to include a static file to always overwrite next-server?
@antonym commented on GitHub (Oct 30, 2020):
I would suggest trying it with just iPXE by itself and see if the issue still happens. I don't believe there is any code in netboot.xyz rewriting the next-server variable.
@github-actions[bot] commented on GitHub (Nov 30, 2020):
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.
@antonym commented on GitHub (Jul 8, 2021):
Closing due to no activity.