On Saturday 25 August 2007 03:00:24 Jim Kronebusch wrote:
> On Fri, 24 Aug 2007 17:11:28 +0700, Fajar Priyanto wrote
>
> > Hello all,
> > I took this part of dhcpd.conf from Jim Kronebusch yesterday :)
> > I have a situation where the LTSP5 clients is located in the same network
> > as the non-LTSP clients. Therefore I believe we can use the host
> > declaration based on MAC address.
> >
> > But, I'm sure about the correct syntax. I need to setup DHCP on this
> > case: Clients are divided into 3 groups:
> > Group A: 192.168.0.1-192.168.0.10 (Non-LTSP clients)
> > Group B: 192.168.0.50-192.168.0.60 (Non-LTSP clients, notice the gap of
> > IP range from Group A).
> > Group C: 192.168.0.100-192.168.0.130 (LTSP clients).
>
> I believe the following should do what you want. Of course use your domain
> name server, your router ip, and change mac addresses for fixed hosts. To
> add the other 28 LTSP clients duplicate this portion for all needed
> clients:
> host client1 {
> hardware ethernet 00:1A:4D:2F:A5:78;
> fixed-address 192.168.0.100;
> }
>
> I hope this helps you out. Jim
> --------------dhcpd.conf-------------------------------
>
> # Main LAN IP Range
> subnet 192.168.0.0 netmask 255.255.255.0 {
> option domain-name "yourdomain.org";
> option domain-name-servers 192.168.0.254;
> option routers 192.168.0.254;
> option subnet-mask 255.255.255.0;
> pool {
> allow unknown-clients;
> range 192.168.0.1 192.168.0.10;
> }
> pool {
> allow unknown-clients;
> range 192.168.0.50 192.168.0.60;
> }
> }
> # LTSP5 Clients by Mac address
> group {
> use-host-decl-names on;
> deny unknown-clients;
> if substring( option vendor-class-identifier , 0 , 9 ) = "PXEClient"
> { filename "/ltsp/i386/pxelinux.0";
> }
> else {
> filename "/ltsp/i386/nbi.img";
> }
> option root-path "/opt/ltsp/i386";
> host client1 {
> hardware ethernet 00:1A:4D:2F:A5:78;
> fixed-address 192.168.0.100;
> }
> host client2 {
> hardware ethernet 00:1A:4D:GF:HR:56;
> fixed-address 192.168.0.101;
> }
> }
Hello Jim,
Thank you so much for the direction.
I've followed it and now am able to partition the network using dhcp as you
stated.
However I'm stuck on the next-server parameter. You see, I put the dhcp server
on a different server other than the LTSP server. For this I use the
next-server parameter. Client can get the assigned IP (192.168.0.100), but
failed to contact the TFTP server.
=================
This is my dhcpd.conf as per your help:
=================
authoritative;
server-identifier centos5a;
ddns-updates on;
ddns-update-style interim;
ddns-domainname "jauh.com.";
ddns-rev-domainname "in-addr.arpa.";
ignore client-updates;
include "/etc/ddns_key.key";
subnet 192.168.0.0 netmask 255.255.255.0 {
option domain-name "jauh.com";
option domain-name-servers 192.168.0.199, 10.1.2.253;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
option subnet-mask 255.255.255.0;
next-server 192.168.0.197;
pool {
allow unknown-clients;
range 192.168.0.20 192.168.0.30;
}
pool {
deny unknown-clients;
range 192.168.0.50 192.168.0.60;
host nonltsp1 {
hardware ethernet 00:16:11:23:30:9f;
fixed-address 192.168.0.50;
}
}
#}
#LTSP Clients by Mac Address
group {
use-host-decl-names on;
deny unknown-clients;
# TFTP server address:
next-server 192.168.0.197;
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
}
else{
filename "/ltsp/i386/nbi.img";
}
option root-path "/opt/ltsp/i386";
host client1 {
hardware ethernet 00:16:17:23:30:9f;
fixed-address 192.168.0.100;
}
}
}
zone jauh.com. {
primary 192.168.0.199;
key ddns_key;
}
zone 0.168.192.in-addr.arpa. {
primary 192.168.0.199;
key ddns_key;
}
================
This is my original working dhcpd.conf:
================
authoritative;
server-identifier centos5a;
ddns-updates on;
ddns-update-style interim;
ddns-domainname "jauh.com.";
ddns-rev-domainname "in-addr.arpa.";
ignore client-updates;
include "/etc/ddns_key.key";
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.50 192.168.0.100;
option domain-name "jauh.com";
option domain-name-servers 192.168.0.199, 10.1.2.253;
option broadcast-address 192.168.0.255;
option routers 192.168.0.254;
# TFTP server address:
next-server 192.168.0.197;
option subnet-mask 255.255.255.0;
if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
filename "/ltsp/i386/pxelinux.0";
}
else{
filename "/ltsp/i386/nbi.img";
}
option root-path "/opt/ltsp/i386";
}
zone jauh.com. {
primary 192.168.0.199;
key ddns_key;
}
zone 0.168.192.in-addr.arpa. {
primary 192.168.0.199;
key ddns_key;
}
I believe this is syntax related issue, don't you think so?
Best regards,
--
Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial
http://linux2.arinet.org
17:07:54 up 3:28, 2.6.20-16-generic GNU/Linux
Let's use OpenOffice. http://www.openoffice.org
pgpcNv1Tx4kQ2.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
