mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 15:15:56 +03:00
[GH-ISSUE #185] issue with vlan? #87
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#87
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 @o0-o on GitHub (Sep 26, 2017).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/185
Having an issue that appears to be caused by vlan tagging, or maybe a DHCP quirk.
netboot.xyz loads to the point of connecting to boot.netboot.xyz/menu.ipxe and then fails.
I am only seeing this in when vlans are in play. The traffic is being tagged by the switch (not a trunk or anything), so should be invisible to netboot...
The odd thing is that if I manually enter the network info exactly as the DHCP server would assign it, then everything works. I was able to install CentOS without any problems. Once netboot loads the CentOS installer, the DHCP address is picked up and everything is normal.
The attached screenshot is from vm but I am also seeing this on physical servers.
Any ideas?
@o0-o commented on GitHub (Sep 27, 2017):
After further testing, I found an issue with my DNS configuration on my DHCP server.
The only issue here is that netboot.xyz will not use a secondary DNS server provided by a DHCP server. This is why it was failing while installed OS's were not having issues.
@antonym commented on GitHub (Sep 27, 2017):
Cool, glad you got it fixed. Yeah, I think iPXE will only use the first DNS server provided.