I have a network of virtual machines, three of which are Docker VMs
(boot2docker distribution) and the fourth is a turnkeylinux core server
running isc-dhcp-server.
I have assigned specific IPs to MAC addresses corresponding to the three
Docker VMs and set up a pool of adresses for any other machines on the
network (ie. if a new Docker VM is created, DHCP server should assing it one
of the IPs from the pool).
The problem is that while the server sends DHCPOFFER with the IP assigned to
given MAC, the client responds with DHCPREQUEST and then DHCPNAK for default
Docker VM IP.
My dhcp.conf:
ddns-update-style none;
option domain-name "docker";
option domain-name-servers 10.132.251.2,10.132.33.41;
default-lease-time 60000;
max-lease-time 72000;
authoritative;
log-facility local7;
subnet 192.168.99.0 netmask 255.255.255.0 {
range 192.168.99.101 192.168.99.254;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.99.255;
option routers 192.168.99.1;
}
host default {
hardware ethernet 08:00:27:5B:78:24;
fixed-address 192.168.99.100;
}
host jenkins {
hardware ethernet 08:00:27:70:52:3C;
fixed-address 192.168.99.10;
}
host test {
hardware ethernet 08:00:27:09:8A:14;
fixed-address 192.168.99.11;
}
The syslog of communication between client and server:
Sep 18 08:38:57 core dhcpd: DHCPDISCOVER from 08:00:27:09:8a:14 via eth1
Sep 18 08:38:57 core dhcpd: DHCPOFFER on 192.168.99.11 to 08:00:27:09:8a:14
via eth1
Sep 18 08:38:57 core dhcpd: DHCPREQUEST for 192.168.99.100 (192.168.99.6)
from 08:00:27:09:8a:14 via eth1: lease 192.168.99.100 unavailable.
Sep 18 08:38:57 core dhcpd: DHCPNAK on 192.168.99.100 to 08:00:27:09:8a:14
via eth1
Can someone tell me what I'm doing wrong? Or for that matter whether it's an
issue with DHCP server's or Docker VM's settings?
--
Sent from:
http://isc-dhcp-users.2343191.n4.nabble.com/_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Locked
