Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Changes in dhcpd.conf do not make a difference in DHCP service behaviour Post 303031954 by ekorgur on Friday 8th of March 2019 05:42:42 AM
Old 03-08-2019
I couldnt get the OS version yet. DHCP server is administrated by somebody else. I will update it soon.
DHCP Server 4.1.1-P1

I mentioned before that I was going to copy the /etc/dhcpd.conf to /etc/dhcp/dhcpd.conf
I did that and restarted the service.
Now I started to receive a new kind of error and the service doesnt start. How it was working before with /etc/dhcpd.conf is still something I have no idea.

Code:
Mar  7 16:19:30 trber dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Mar  7 16:19:30 trber dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Mar  7 16:19:30 trber dhcpd: All rights reserved.
Mar  7 16:19:30 trber dhcpd: For info, please visit .......
Mar  7 16:19:30 trber dhcpd: WARNING: Host declarations are global.  They are not limited to the scope you declared them in.
Mar  7 16:19:30 trber dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Mar  7 16:19:30 trber dhcpd: Wrote 0 deleted host decls to leases file.
Mar  7 16:19:30 trber dhcpd: Wrote 0 new dynamic host decls to leases file.
Mar  7 16:19:30 trber dhcpd: Wrote 0 leases to leases file.
Mar  7 16:19:30 trber dhcpd:
Mar  7 16:19:30 trber dhcpd: No subnet declaration for eth0 (10.210.148.7).
Mar  7 16:19:30 trber dhcpd: ** Ignoring requests on eth0.  If this is not what
Mar  7 16:19:30 trber dhcpd:    you want, please write a subnet declaration
Mar  7 16:19:30 trber dhcpd:    in your dhcpd.conf file for the network segment
Mar  7 16:19:30 trber dhcpd:    to which interface eth0 is attached. **
Mar  7 16:19:30 trber dhcpd:
Mar  7 16:19:30 trber dhcpd:
Mar  7 16:19:30 trber dhcpd: Not configured to listen on any interfaces!
Mar  7 16:19:30 trber dhcpd:
Mar  7 16:19:30 trber dhcpd: This version of ISC DHCP is based on the release available
Mar  7 16:19:30 trber dhcpd: on ftp.isc.org.  Features have been added and other changes
Mar  7 16:19:30 trber dhcpd: have been made to the base software release in order to make
Mar  7 16:19:30 trber dhcpd: it work better with this distribution.
Mar  7 16:19:30 trber dhcpd:
Mar  7 16:19:30 trber dhcpd: Please report for this software via the Red Hat Bugzilla site:
Mar  7 16:19:30 trber dhcpd:     ......
Mar  7 16:19:30 trber dhcpd:
Mar  7 16:19:30 trber dhcpd: exiting.

Subnet declaration was defined as below.

Code:
ddns-update-style none;

subnet 172.17.126.192 netmask 255.255.255.224 {
   option broadcast-address 172.17.126.223;
   next-server 172.17.126.195;
   option routers 172.17.126.195;

   host fsb1 {
      option host-name "fsb1";
      option root-path "/gsn/nodes/fsb1";
      hardware ethernet XX:XX:XX:XX:45:06;
      fixed-address 172.17.126.200;
      filename "/BootFiles/fsb_gep3/linux/kernel/pxelinux.0";
   }

Because of the error seen in messages logs, or something else, the dhcpd service doesnt work anymore.
 

10 More Discussions You Might Find Interesting

1. Linux

dhcpd.conf

I have intall a REdhat 9.0 as a server and Ive configure to act as a DHCP however Im having technical problems b/c the file /etc/dhcpd.conf does not exists. I went to the text edit and I created : subnet 192.192.168.100.0 netmask 255.255.255.0 { range 192.168.100.10 192.168.100.150;... (1 Reply)
Discussion started by: keliy1
1 Replies

2. Solaris

DHCP Service

Thanks for reply , i realy love using unix ... is there anyone who can give me an instruction to configure DHCP Server in Sun Solaris 10 just a quick guide .. i know how to configure DHCP Server in Windows operating System ..But i want also learn how to configure it from the SUN SOLARIS 10...... (6 Replies)
Discussion started by: giancarlodjabon
6 Replies

3. Shell Programming and Scripting

Shell/Perl Script to edit dhcpd.conf

Hi, I need to get a script together to edit the dhcp service configuration file dhcpd.conf. Mac addresses are defined in classes ex. class "HOST1" { match if substring (hardware, 1,18)=00:11:11:FF:FF:FF;} class "HOST2" ... class "HOST3" ... ... followed by allow or deny statements:... (4 Replies)
Discussion started by: sahilb
4 Replies

4. Linux

dhcpd.conf - static route

Hi, I've setup DHCP Server on RH linux AS3 and everything works fine except static routes. They are not getting effected on client systems. My dhcpd.conf: +++++++++++ ddns-update-style interim; ddns-updates off; option domain-name-servers 192.168.116.122; option domain-name... (3 Replies)
Discussion started by: prvnrk
3 Replies

5. Shell Programming and Scripting

delete dhcp.conf entry using sed

I am trying to use sed to remove entries from my dhcpd.conf file. The form of the file is: host foo { option 1 option 2 } host bar { option 1 option 2 } I was trying to use a label like: sed -e :a -e "s/^host bar {*//g;/{/N;//ba" /etc/dhcpd.conf... (2 Replies)
Discussion started by: tizatron
2 Replies

6. Solaris

Solaris Install over WAN(where to keep wanboot.conf file for DHCP client)

I am trying to configure my jumpstart server to install Solaris 10 on a T1000 machine(target) over WAN. I do not know the IP address of the client, i wish the client to get the IP address from DHCP. how do i configure my /etc/netboot hierarchy. One option would be to keep the wanboot.conf in... (1 Reply)
Discussion started by: hemalsid
1 Replies

7. UNIX for Dummies Questions & Answers

Difference between configure/make/make install.

Hi, While installation of apache on linux, we perform the below tasks. 1) Untar 2) configure 3) make 4) make install. I wanted to understand the difference and working of configure/make/make install. Can any one help me understanding this? Thanks in advance. (1 Reply)
Discussion started by: praveen_b744
1 Replies

8. Shell Programming and Scripting

Help with Perl to change dhcpd.conf file

Hi all, I am too new for this stuff and i am lost in perl tutorials. I need help to change dhcp entries in .conf file with a perl script. The file entries are like below : host bertha-clp-0 { hardware ethernet AA:0A:A0:00:6c:40; fixed-address 10.10.10.72; option... (6 Replies)
Discussion started by: ekckabatop
6 Replies

9. Shell Programming and Scripting

Shell Script to check dhcp conf file

Hi, I have to prepare a script to check the dhcp conf file. The script has to check for a specific parameter called circuit ID. If the Circuit ID is unique it should show the output that it is unique and if it is duplicate it should show that the Circuit ID is duplicate. I have prepared the... (4 Replies)
Discussion started by: Crazy_Nix
4 Replies

10. Shell Programming and Scripting

Listing IPs from the dhcpd.conf

Hy everybody, Within a dhcpd.conf file, we got some fixed IP adresses from 192.168.0.1 - 192.168.0.254. Sample: #ddns-update-style interim; ddns-update-style none; ignore client-updates; deny client-updates; authoritative; #### By red for PXE Booting allow booting; allow bootp; ###... (17 Replies)
Discussion started by: hermouche
17 Replies
dhcpd.leases(5) 						File Formats Manual						   dhcpd.leases(5)

NAME
dhcpd.leases - DHCP client lease database DESCRIPTION
The Internet Systems Consortium DHCP Server keeps a persistent database of leases that it has assigned. This database is a free-form ASCII file containing a series of lease declarations. Every time a lease is acquired, renewed or released, its new value is recorded at the end of the lease file. So if more than one declaration appears for a given lease, the last one in the file is the current one. When dhcpd is first installed, there is no lease database. However, dhcpd requires that a lease database be present before it will start. To make the initial lease database, just create an empty file called /var/lib/dhcpd/dhcpd.leases. You can do this with: touch /var/lib/dhcpd/dhcpd.leases In order to prevent the lease database from growing without bound, the file is rewritten from time to time. First, a temporary lease database is created and all known leases are dumped to it. Then, the old lease database is renamed /var/lib/dhcpd/dhcpd.leases~. Finally, the newly written lease database is moved into place. FORMAT
Lease descriptions are stored in a format that is parsed by the same recursive descent parser used to read the dhcpd.conf(5) and dhclient.conf(5) files. Lease files can contain lease declarations, and also group and subgroup declarations, host declarations and failover state declarations. Group, subgroup and host declarations are used to record objects created using the OMAPI protocol. The lease file is a log-structured file - whenever a lease changes, the contents of that lease are written to the end of the file. This means that it is entirely possible and quite reasonable for there to be two or more declarations of the same lease in the lease file at the same time. In that case, the instance of that particular lease that appears last in the file is the one that is in effect. Group, subgroup and host declarations in the lease file are handled in the same manner, except that if any of these objects are deleted, a rubout is written to the lease file. This is just the same declaration, with { deleted; } in the scope of the declaration. When the lease file is rewritten, any such rubouts that can be eliminated are eliminated. It is possible to delete a declaration in the dhcpd.conf file; in this case, the rubout can never be eliminated from the dhcpd.leases file. THE LEASE DECLARATION
lease ip-address { statements... } Each lease declaration includes the single IP address that has been leased to the client. The statements within the braces define the duration of the lease and to whom it is assigned. starts date; ends date; tstp date; tsfp date; atsfp date; cltt date; The start and end time of a lease are recorded using the starts and ends statements. The tstp statement is specified if the failover pro- tocol is being used, and indicates what time the peer has been told the lease expires. The tsfp statement is also specified if the failover protocol is being used, and indicates the lease expiry time that the peer has acknowledged. The atsfp statement is the actual time sent from the failover partner. The cltt statement is the client's last transaction time. The date is specified in two ways, depending on the configuration value for the db-time-format parameter. If it was set to default, then the date fields appear as follows: weekday year/month/day hour:minute:second The weekday is present to make it easy for a human to tell when a lease expires - it's specified as a number from zero to six, with zero being Sunday. The day of week is ignored on input. The year is specified with the century, so it should generally be four digits except for really long leases. The month is specified as a number starting with 1 for January. The day of the month is likewise specified start- ing with 1. The hour is a number between 0 and 23, the minute a number between 0 and 59, and the second also a number between 0 and 59. Lease times are specified in Universal Coordinated Time (UTC), not in the local time zone. There is probably nowhere in the world where the times recorded on a lease are always the same as wall clock times. On most unix machines, you can display the current time in UTC by typing date -u. If the db-time-format was configured to local, then the date fields appear as follows: epoch <seconds-since-epoch>; # <day-name> <month-name> <day-number> <hours>:<minutes>:<seconds> <year> The seconds-since-epoch is as according to the system's local clock (often referred to as "unix time"). The # symbol supplies a comment that describes what actual time this is as according to the system's configured timezone, at the time the value was written. It is pro- vided only for human inspection. If a lease will never expire, date is never instead of an actual date. hardware hardware-type mac-address; The hardware statement records the MAC address of the network interface on which the lease will be used. It is specified as a series of hexadecimal octets, separated by colons. uid client-identifier; The uid statement records the client identifier used by the client to acquire the lease. Clients are not required to send client identi- fiers, and this statement only appears if the client did in fact send one. Client identifiers are normally an ARP type (1 for ethernet) followed by the MAC address, just like in the hardware statement, but this is not required. The client identifier is recorded as a colon-separated hexadecimal list or as a quoted string. If it is recorded as a quoted string and it contains one or more non-printable characters, those characters are represented as octal escapes - a backslash character followed by three octal digits. client-hostname hostname ; Most DHCP clients will send their hostname in the host-name option. If a client sends its hostname in this way, the hostname is recorded on the lease with a client-hostname statement. This is not required by the protocol, however, so many specialized DHCP clients do not send a host-name option. abandoned; The abandoned statement indicates that the DHCP server has abandoned the lease. In that case, the abandoned statement will be used to indicate that the lease should not be reassigned. Please see the dhcpd.conf(5) manual page for information about abandoned leases. binding state state; next binding state state; The binding state statement declares the lease's binding state. When the DHCP server is not configured to use the failover protocol, a lease's binding state will be either active or free. The failover protocol adds some additional transitional states, as well as the backup state, which indicates that the lease is available for allocation by the failover secondary. The next binding state statement indicates what state the lease will move to when the current state expires. The time when the current state expires is specified in the ends statement. option agent.circuit-id string; option agent.remote-id string; The option agent.circuit-id and option agent.remote-id statements are used to record the circuit ID and remote ID options send by the relay agent, if the relay agent uses the relay agent information option. This allows these options to be used consistently in conditional eval- uations even when the client is contacting the server directly rather than through its relay agent. set variable = value; The set statement sets the value of a variable on the lease. For general information on variables, see the dhcp-eval(5) manual page. The ddns-text variable The ddns-text variable is used to record the value of the client's TXT identification record when the interim ddns update style has been used to update the DNS for a particular lease. The ddns-fwd-name variable The ddns-fwd-name variable records the value of the name used in updating the client's A record if a DDNS update has been successfully done by the server. The server may also have used this name to update the client's PTR record. The ddns-client-fqdn variable If the server is configured to use the interim ddns update style, and is also configured to allow clients to update their own fqdns, and the client did in fact update its own fqdn, then the ddns-client-fqdn variable records the name that the client has indicated it is using. This is the name that the server will have used to update the client's PTR record in this case. The ddns-rev-name variable If the server successfully updates the client's PTR record, this variable will record the name that the DHCP server used for the PTR record. The name to which the PTR record points will be either the ddns-fwd-name or the ddns-client-fqdn. The vendor-class-identifier variable The server retains the client-supplied Vendor Class Identifier option for informational purposes, and to render them in DHCPLEASEQUERY responses. on events { statements... } The on statement records a list of statements to execute if a certain event occurs. The possible events that can occur for an active lease are release and expiry. More than one event can be specified - if so, the events are separated by '|' char- acters. bootp; reserved; These two statements are effectively flags. If present, they indicate that the BOOTP and RESERVED failover flags, respec- tively, should be set. BOOTP and RESERVED dynamic leases are treated differently than normal dynamic leases, as they may only be used by the client to which they are currently allocated. THE FAILOVER PEER STATE DECLARATION
The state of any failover peering arrangements is also recorded in the lease file, using the failover peer statement: failover peer name state { my state state at date; peer state state at date; } The states of the peer named name is being recorded. Both the state of the running server (my state) and the other failover partner (peer state) are recorded. The following states are possible: unknown-state, partner-down, normal, communications-interrupted, resolution- interrupted, potential-conflict, recover, recover-done, shutdown, paused, and startup. FILES
/var/lib/dhcpd/dhcpd.leases /var/lib/dhcpd/dhcpd.leases~ SEE ALSO
dhcpd(8), dhcp-options(5), dhcp-eval(5), dhcpd.conf(5), RFC2132, RFC2131. AUTHOR
dhcpd(8) was written by Ted Lemon under a contract with Vixie Labs. Funding for this project was provided by Internet Systems Consortium. Information about Internet Systems Consortium can be found at: https://www.isc.org/ dhcpd.leases(5)
All times are GMT -4. The time now is 08:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy