[GH-ISSUE #185] issue with vlan? #87

Closed
opened 2026-02-27 14:50:18 +03:00 by kerem · 2 comments
Owner

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?

screen shot 2017-09-26 at 3 45 01 pm

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? ![screen shot 2017-09-26 at 3 45 01 pm](https://user-images.githubusercontent.com/17324878/30881310-60c32f48-a2d3-11e7-8c05-ef3466d73269.png)
kerem closed this issue 2026-02-27 14:50:18 +03:00
Author
Owner

@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.

<!-- gh-comment-id:332650101 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:332659760 --> @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.
Sign in to join this conversation.
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#87
No description provided.