James Knott wrote:

You most certainly can have more than one DHCP server. You just have to make sure they don't try to hand out the same address. The easiest way is to give them different address pools. For example, if your DHCP range is .100 to .199, then one server issues .100 - .149 and the other, .150 - .199. All other settings (default route etc.) would be the same

Forgot to mention, there may be occasions when the settings are different. For example, if you have more than one internet connection, you may assign different default routes as a crude method of load balancing. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

Anthony M Simonelli wrote:

...

My guess is that the thin client thinks the DHCP server (Windows NT 4 Server) is also the TFTPBoot server so it times out looking for the TFTPBoot server as well. When it did work, it must have gotten the DHCP request answered by the KIWI-LTSP server and it correctly booted but I can't have two DHCP servers running on the same LAN.

I think I'm having the same problem as this person: http://www.linuxquestions.org/questions/linux-networking-3/opensuse-kiwi-lts... but I already have the TFTP server address defined in the Windows NT DHCP server. Does anyone know how to configure the KIWI-LTSP server to use a different DHCP server like my Windows NT DHCP server? Also, what DHCP options are necessary for the thin clients?

A device looking for a DHCP server will generally accept the first one to respond. You can't pick a specific one. Perhaps you could add a TFTP server to the KIWI-LTSP settings.

Hi, I havent used this before, but, cant you just have each server hand out different subnets so they dont conflict with each other? -- Steve Reilly http://reillyblog.com "Any people anywhere, being inclined, and having the power, have the right to rise up and shake off the existing government, and form a new one that suits them better." Abraham Lincoln 1848 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2008-11-14 at 16:14 -0500, James Knott wrote:

steve wrote:

...

James Knott wrote:

...

Anthony M Simonelli wrote:

...

My guess is that the thin client thinks the DHCP server (Windows NT 4 Server) is also the TFTPBoot server so it times out looking for the TFTPBoot server as well. When it did work, it must have gotten the DHCP request answered by the KIWI-LTSP server and it correctly booted but I can't have two DHCP servers running on the same LAN.

I think I'm having the same problem as this person: http://www.linuxquestions.org/questions/linux-networking-3/opensuse-kiwi-lts... but I already have the TFTP server address defined in the Windows NT DHCP server. Does anyone know how to configure the KIWI-LTSP server to use a different DHCP server like my Windows NT DHCP server? Also, what DHCP options are necessary for the thin clients?

A device looking for a DHCP server will generally accept the first one to respond. You can't pick a specific one. Perhaps you could add a TFTP server to the KIWI-LTSP settings.

Hi, I havent used this before, but, cant you just have each server hand out different subnets so they dont conflict with each other?

The problem then becomes which DHCP server responds. When a device wants an address, it sends a broadcast to the network. Any DHCP servers will then respond and the device then goes with the 1st one it hears. I suppose you might be able to blacklist a particular MAC, but I've never seen it done.

-- Use OpenOffice.org http://www.openoffice.org

Thank you so much for your responses. Basically, I have an Ubuntu LTSP setup right now, with the DHCP server disabled. On the Windows NT server, I have reserved IP address from the DHCP pool based on the MAC addresses of the thin clients and have assigned specific DHCP options for them (Boot File Size, Root Path, Boot Server Host Name, etc.). I thought there was a way to use the Windows NT DHCP server to pass the correct parameters to the thin clients that would work with the KIWI-LTSP setup so I didn't have to run the DHCP server. Maybe there is a way to configure the DHCP server on the KIWI-LTSP to only hand out IP address based on MAC address and forward other requests? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

CyberOrg wrote:

On Sat, Nov 15, 2008 at 7:58 AM, Anthony M Simonelli wrote:

...

Maybe there is a way to configure the DHCP server on the KIWI-LTSP to only hand out IP address based on MAC address and forward other requests?

Configure /etc/dhcpd.conf on the server to serve only selected MAC addresses. Something like the following after adding all IP addresses to server /etc/hosts.

host ws150 { hardware ethernet 00:0C:29:74:70:C1; fixed-address 192.168.1.150; filename "/pxelinux.0"; }

Ciao

-J

Is there no way to add other DHCP parameters to the DHCP server? I don't see anything in the Yast DHCP config, but in the sysconfig editor, there is a box for adding parameters. Perhaps there? On other equipment I work on, they have the usual suspects, such as default route, WINS, NDS etc., but also a method of adding the various DHCP numbered options. Can that sort of thing be done in the SUSE DHCP server? -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org