LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 02-23-2010, 10:18 AM   #1
cuthieu
LQ Newbie
 
Registered: Feb 2010
Posts: 3

Rep: Reputation: 0
Configure/Setup DHCP, TFTP servers


I've tried to configure DRBL server to use Clonezilla and that is required me to setup DHCP, TFTP servers. But I've gotten a lot of errors from them - so please look at my attachments from /var/log/messages and dhcpd.conf - help me to find out what are wrong with them. Thanks so much

Feb 23 09:47:46 eth0-eth0 last message repeated 17 times
Feb 23 09:55:06 eth0-eth0 dhcpd: DHCPREQUEST for 192.168.1.53 from 00:13:20:36:26:28 via eth0: unknown lease 192.168.1.53.
Feb 23 09:57:10 eth0-eth0 dhcpd: DHCPREQUEST for 192.168.1.47 from 00:13:20:4e:64:87 via eth0: unknown lease 192.168.1.47.
Feb 23 09:57:14 eth0-eth0 dhcpd: DHCPREQUEST for 192.168.1.47 from 00:13:20:4e:64:87 via eth0: unknown lease 192.168.1.47.
Feb 23 09:57:30 eth0-eth0 dhcpd: DHCPREQUEST for 192.168.1.46 from 00:1c:23:20:ea:5e via eth0: unknown lease 192.168.1.46.
Feb 23 09:58:52 eth0-eth0 dhcpd: DHCPINFORM from 192.168.1.111 via eth0: not authoritative for subnet 192.168.1.0
Feb 23 10:00:04 eth0-eth0 dhcpd: DHCPDISCOVER from 00:21:70:b0:f4:5b via eth0: network 192.168.1/24: no free leases
Feb 23 10:00:04 eth0-eth0 dhcpd: DHCPREQUEST for 192.168.1.48 (192.168.1.2) from 00:21:70:b0:f4:5b via eth0: unknown lease 192.168.1.48.
Feb 23 10:01:16 eth0-eth0 dhcpd: DHCPINFORM from 192.168.1.48 via eth0: not authoritative for subnet 192.168.1.0
Feb 23 10:01:55 eth0-eth0 dhcpd: DHCPINFORM from 192.168.1.34 via eth0: not authoritative for subnet 192.168.1.0
Feb 23 10:06:27 eth0-eth0 dhcpd: DHCPDISCOVER from 00:1c:23:16:67:55 via eth0: network 192.168.1/24: no free leases
Feb 23 10:06:27 eth0-eth0 dhcpd: DHCPREQUEST for 192.168.1.73 (192.168.1.2) from 00:1c:23:16:67:55 via eth0: unknown lease 192.168.1.73.



# Generated by DRBL.
# Do NOT modify this file unless you know what you are doing!


allow booting;
allow bootp;
filename = "/tftpboot/pxelinux.0";
athoritative;


default-lease-time 300;
max-lease-time 300;
option subnet-mask 255.255.255.0;
option domain-name-servers 63.103.85.38,192.5.6.34,192.35.51.34;
option domain-name "femmecomp.com";
ddns-update-style none;
server-name drbl;


filename = "/tftpboot/pxelinux.0";

# gpxelinux.0 features: HTTP, DNS, TFTP, iSCSI, AoE, bzImage ELF, Multiboot, PXE, PXEXT. Ref: http://ols.fedoraproject.org/OLS/Rep...in-reprint.pdf
# filename = "gpxelinux.0";

## Uncomment the following "if block" when you have some buggy PXE NIC card (such as annoying sis900 NIC). Remember to modify the MAC vendor prefix and restart dhcpd service!!!
## This is a workround for some network card with BAD PXE code in firmware.
## It will only affect those clients with MAC vendor prefix you assigned.
## Ref: http://syslinux.zytor.com/archives/2...st/005640.html


#if substring (option vendor-class-identifier, 0, 3) = "PXE" {
# # **************************************************************
# # ***MODIFY*** the MAC vendor prefix of client network card here.
# # **************************************************************
# # For annoying sis900 network card, maybe it is 00:07:95, 00:0C:6E...
# if substring (hardware, 1, 3) = 00:0C:6E {
# # eb-5.4.3-etherboot-pci.zpxe is a all-in-one pxe image, works for most NIC.
# # sis900.zpxe is specially for sis900 NIC.
# # Try either one.
# #filename = "eb-5.4.3-etherboot-pci.zpxe";
# filename = "sis900.zpxe";
# }
#}

# Uncomment the following to get the debug/verbose messages in system log. The messages like the following will be shown:
# Client 0:c:29:3b:34:fb requests 1:2:3:5:6:b:c:d:f:10:11:12:2b:36:3c:43:80:81:82:83:84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
# Client 0:c:29:3b:34:fb requests 1:3:6:c:f:1c:28:29:2a - DRBLClient - no dhcp-client-id
# Begin of log command
log(info, concat("Client ",
binary-to-ascii(16, 8, ":", substring(hardware, 1, 6)),
" requests ",
binary-to-ascii(16, 8, ":", option dhcp-parameter-request-list),
" - ",
pick-first-value(option vendor-class-identifier, "no vendor-id"),
" - ",
pick-first-value(option dhcp-client-identifier, "no dhcp-client-id"))
);
# End of log command

# This class 'DRBL-Client' defines 3 kind of clients: PXE, Etherboot (1st stage) or DRBL client (2nd stage, i.e. in network initrd/initramfs (mkpxeinitrd-net)) to lease IP address. This will only affect 'range' statement only, not the 'host' statement.
# Note! The following line(s) in the pool statement: 'allow members of "DRBL-Client";' is/are commented to disable this mechanism by default.
# If you do want to use this mechanism, uncomment all 'allow members of "DRBL-Client";', then only PXE, etherboot and DRBL client can lease IP address from this DHCP service.
# ///NOTE/// In summary, two cases you can turn on this mechanism:
# (1) This DRBL server is not used as a clonezilla server.
# (2) This DRBL server is used as a Clonezilla server, with the following conditions:
# (a) 'range' statement is used in this DRBL service.
# (b) There is an existing DHCP service which can provide IP address leases to the restored OS (either GNU/inux or MS Windows) in the client. Otherwise if you uncomment 'allow members of "DRBL-Client";', restored OS won't be able to lease IP address.

# The DRBL client class: PXE, Etherboot or DRBL client
class "DRBL-Client" {
match if
(substring(option vendor-class-identifier, 0, 9) = "PXEClient") or
(substring(option vendor-class-identifier, 0, 9) = "Etherboot") or
(substring(option vendor-class-identifier, 0, 10) = "DRBLClient") ;
}

# If you want to use special port for DHCP service, edit here:
# For more info, ref: http://drbl.sourceforge.net/faq/inde...sting_dhcp.faq
# local-port 1067;
# remote-port 1068;

subnet 192.168.1.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option routers 192.5.6.34;
next-server 192.168.1.61;

pool {
allow members of "DRBL-Client";
range 192.168.1.1 192.168.1.2;
deny unknown clients;
}
}
 
Old 02-24-2010, 03:12 AM   #2
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 16,256

Rep: Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321Reputation: 2321
I've set this up recently. Most distros have a document on this - slackware certainly does.Why not follow that? What's yopur distro?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP & TFTP Debugs cuthieu Linux - Server 1 02-24-2010 09:21 PM
FOG DHCP PXE TFTP question mpmackenna Linux - Server 2 12-25-2009 06:10 PM
PXE, DHCP, TFTP, Working - Bootable image not!?!? almcneill Linux - Networking 4 07-25-2008 03:06 PM
Network Install using PXe, DHCP, TFTP and FTP Aseem SUSE / openSUSE 1 12-15-2005 10:57 PM
Network install - TFTP, DHCP, but do I need NFS? redthor Linux - Networking 1 07-07-2005 01:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 07:17 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration