6

Here's my /etc/dhcp3/dhclient.conf:

request subnet-mask, broadcast-address, time-offset, routers,
        domain-name, domain-name-servers, domain-search, host-name,
        netbios-name-servers, netbios-scope, interface-mtu;
timeout 60;
alias {
  interface "eth0";
  fixed-address 192.168.1.222;
}
lease {
  interface "eth0";
  fixed-address 192.168.1.222;
  option subnet-mask 255.255.255.0;
  option broadcast-address 255.255.255.255;
  option routers 192.168.1.254;
  option domain-name-servers 192.168.1.254;
}

When I run "dhclient eth0", I get this:

There is already a pid file /var/run/dhclient.pid with pid 6511
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:1c:25:97:82:20
Sending on   LPF/eth0/00:1c:25:97:82:20
Sending on   Socket/fallback
DHCPREQUEST of 192.168.1.27 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.27 from 192.168.1.254
bound to 192.168.1.27 -- renewal in 1468 seconds.

I used strace to make sure that dhclient really is reading that conf file. Why isn't it paying attention to my "fixed-address 192.168.1.222" line? Why is it doing a DHCPREQUEST for 192.168.1.27 instead?

mike
  • 3,963
  • 11
  • 30
  • 27

3 Answers3

11

As Zoredache correctly pointed out: the fixed-address setting is only for lease definitions that are effective only if the DHCP server does not respond. See http://linux.die.net/man/5/dhclient.conf under section "Lease Declarations".

What you want is

interface "eth0" {
    send dhcp-requested-address 192.168.1.222;
}

This is documented in the manpage of dhcp-options: http://linux.die.net/man/5/dhcp-options and conforms to the DHCP Options RFC available at http://www.rfc-editor.org/rfc/rfc2132.txt

Take note though: I lately run into dhclient3 not getting an IP with this configuration as the requested address was already taken. The server replies with DHCPNAK to the request, and the client will give up after a while. I had expected that the DHCP client will eventually end up with another address if the requested one is not available.

I used this approach in an attempt to make sure that I always know the address of my server without resorting to stuff like dyndns.com and ended up with no connectivity instead.

Bluehorn
  • 281
  • 3
  • 7
7

Reject is for rejecting offers from servers with a specific address. It is not there to reject addresses the server offers.

The reject statement causes the DHCP client to reject offers from servers whose server identifier matches any of the specified hosts or subnets. This can be used to avoid being configured by rogue or mis‐ configured dhcp servers,

A defined lease is only used if the DHCP Server does not respond.

lease { lease-declaration [ ... lease-declaration ] }

The DHCP client may decide after some period of time (see PROTOCOL TIMING) that it is not going to succeed in contacting a server.

If you want a particular address you should probably setup a reservation on the server.

Zoredache
  • 130,897
  • 41
  • 276
  • 420
  • Good info, but one last question: it still says, "DHCPREQUEST of 192.168.1.27 on eth0 to 255.255.255.255 port 67" ... is there any way to force my client to request a particular IP? – mike Mar 29 '10 at 17:26
  • There may be a possible way. I still think you are trying to do this the wrong way. Setup a reservation on the DHCP server, and let the server send the correct address. Past that do a search on `send dhcp-requested-address`. It appears that under some conditions that will allow you to request a specific address. – Zoredache Mar 29 '10 at 20:29
0

Did you actually check if it's accessible via your specified ip (back in 2010, i know...)?

I made that mistake just now.

Your dhclient-output is expected even though you have 

alias{
  fixed-address

That's because thats an alias, as in an additional ip address of that interface; the interface still also get's the dhcp-assigned ip.

Regarding the lease the others are correct, basically it's ignored unless dhcp fails.

beilharz
  • 1