[iconxnoci]

Here is the scenario.. let me know if you can help.

Setup involved:

Ubuntu Box > Linksys WRT54GL > Thin Clients

I have a Linux box that is on Ubuntu. The DHCP server is turned ON on the Ubuntu box since I run thin client solutions from a Linksys WRT54GL router. Because of the way the thin client setup is programmed, I have to have the DHCP server turned OFF on the Linksys router. Now.. the Linux box is programmed with an IP of 192.168.151.10, WRT54GL is set to 192.168.151.1 and the thin clients connect via DHCP per the IP block of 192.168.151.100 – 192.168.151.125. I also have Windows boxes connected to the same Linksys router. Because the DHCP server is turned OFF on the Linksys, and ON on the Linux box, when the Windows computers attempt to get IP address settings via DHCP, the Windows boxes think that the Linux box is the gateway address (192.168.151.10), and therefore cannot connect to the internet.

As far as my question goes.. rather than have a second router thrown into the loop that has DHCP turned on, is there any way to make this work so the Windows computers gather the DHCP settings and use the 192.168.151.1 (Linksys) as the gateway? My thoughts on some ways to do this are rules based on:

1. MAC address of the Windows computers
2. Based on network ID card (eth0)
3. Based on OS type (thin client versus Windows OS)

Any help would be appreciated. You can reply here (I’m subscribed). Thanks in advance.

[WizRd]

edit your dhcpd.conf file and under the scope add

option routers 192.168.151.1;

Save the file and restart dhcpd

[iconxnoci]

Unfortunately I am pretty sure I need that to stay at 192.168.151.10 so the LTSP thin clients know where to get their DHCP address (handed out by the Linux box). I'll give it a try tomorrow and post the results. If anyone has any other ideas to try in the meantime, please reply. Thank you so far WizRd.

[iconxnoci]

Tested and works. Forgot my LTSP clients were hard programmed to get the DHCP address from the server. So easy it hurts. Thanks.