Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
09-21-2009, 05:24 AM
|
#1
|
|
Member
Registered: Sep 2008
Location: Middle of Nowhere, England
Distribution: Slackware 13.1, Ubuntu 10.10
Posts: 38
Rep:
|
PXE boot DHCP too slow.
Hi folks,
Basically the problem is as follows:
I have a couple of Slackware boxes, one PXE booting from the other, and the master connected to the internet via a Draytek Vigor modem/router. During the PXE section of the boot, the DHCP server on the master responds correctly, giving the slave machine it's IP on the correct subnet, and therefore allowing the slave to boot the kernel. During the initial bootup process, however, the kernel issues another DHCP request and the answer it gets is from the Draytek router rather than the master, giving it an IP on a subnet which cannot communicate with the master.
Any ideas would be more than welcome, as I'm totally stumped!
Thanks any and everyone in advance!
X-T
|
|
|
|
09-30-2009, 08:06 PM
|
#2
|
|
LQ Newbie
Registered: Nov 2007
Posts: 9
Rep:
|
It's not legal to have two DHCP servers on the same physical/virtual subnet unless they are synchronized. need to make sure PXE client is not on the physical subnet that the router is on. Either that, or configure router so it points to master as bootparam server. If router has that capability. PXE client will set option 60 (vendor code) to PXEClient. If you have a sophisticated DHCP server on the Draytek you can switch on that.
If the Draydek has a primitive DHCP server, the you are SOL, you're only choice is to isolate the PXE network from the router.
|
|
|
|
12-19-2010, 12:16 AM
|
#3
|
|
Member
Registered: Sep 2008
Location: Middle of Nowhere, England
Distribution: Slackware 13.1, Ubuntu 10.10
Posts: 38
Original Poster
Rep:
|
Hi!
Didn't even realise this had been answered! I eventually got it by setting the IP address on the kernel command line, rather than relying on DHCP. Given that the server will only ever have one client booting from it, I don't know why my predecessor didn't design it this way in the first place! Suffice it to say, that has been changed!
Thanks for your reply, and I apologise for not thanking you for your input sooner!
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:23 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|