[K12OSN] 2 DHCP Servers

[Terrell Prude', Jr.]

Robert Arkiletian wrote:

>However, all got stuck at 
>
>Running dhclient
>mounting root filesystem: /opt/ltsp/i386 from: 192.168.0.254
> 
>and would NOT boot. 
>
>So I disabled eth1 (ifdown eth1) and suddenly ALL clients booted perfectly. 
>Hurray!!!!!!!!!!!!!!!!!!!!!!
>
>Both eth1 and eth0 are plugged into the same hub (I too wish it was a switch, 
>chuck). I'm not sure why eth1 makes such a difference. In any case once all 
>the clients are booted up I (ifup eth1) and internet is back and all is well.
>  
>

><snip>
>

>Wondering if anyone knows what's up with eth1 issue?
>
>Robert Arkiletian
>Eric Hamber Secondary
> 
>

Sounds like you may be running into a routing problem.  That's why I run 
a single-NIC K12LTSP server, which is effectively exactly what you're 
doing right now, after shutting down eth1.  It sounds like you're 
hooking up your thin clients to the school's existing LAN 
infrastructure, just like I do.  That calls for a single-NIC K12LTSP 
install.

The other advantage of the single-NIC install is that other boxes on the 
LAN, e. g. Windows and Mac "fat clients", can use the K12LTSP box as a 
file server via Samba and Netatalk, respectively.

If you do wish to run a dual-NIC K12LTSP server, as is diagrammed on 
www.k12ltsp.org, then you've got to either run VLANs (which means 
managed switches and nothing less), or you've got to have two physically 
separated Layer 3 segments.  eth0 would be on one and eth1 would be on 
the other.  Your thin clients would all need to be on the physical 
segment attached to eth0; any thin clients on the eth1 segment, in this 
kind of setup, will not work without tweaking.  Note that eth1 is 
attached to the school LAN in this type of setup.

--TP