Re: Terminal Server after hd install (fixed Patch)
Unless the boot proms provide for using an alternate port,
I don't think you're going to get very far with that idea.
I can think of a couple of different options:
1: configure the main DHCP server too ignore the MAC
addresses of the slave boxes. -- alternatively (which may be
easier) configure it with the MAC addresses of the boxes
that you DO want it to configure.
2: Insert a bridging firewall between the terminalserver
clients and the main DHCP server that filters out those
requests, but otherwise acts like an intelligent switch.
It could still be configured to allow DHCP requests from specific
boxes on the inside of the firewall (i.e. the server).
3: The last (and possibly best) solution would be to transfer
the necessary DHCP boot info to the master server. This doesn't
affect machines that are doing a normal boot (They'll ignore it),
but anything doing a net boot will then become a ParallelKnoppix
I've actually done this so that my BSD firewall provides the DHCP
info and my diskless boxes boot Knoppix from a Redhat-9 machine
(with all of the pertinent files transferred to it).
Michael Creel wrote:
Hi, I'm the developer of ParallelKnoppix, a remastered Knoppix (thanks,
Klaus, if you happen to see this) which uses the terminal server to boot up
slave nodes in a cluster. At my university, the existing DHCP server often
provides an IP to the slaves before my master node does. I have experimented
with using alternate ports, but never got it to work. My question is, would
the terminal server using this patch work with ordinary PXE boot, not using
rom-o-matic? I prefer not to have to boot up a bunch of nodes using floppy
disks - it is easier just to isolate them from the rest of the network and
let the master node work as PXE and DHCP server. TIA, Michael
--
Stephen Samuel +1(604)876-0426 samnospam@bcgreen.com
http://www.bcgreen.com/
Powerful committed communication. Transformation touching
the jewel within each person and bringing it to light.
Reply to: