Clients Devices Get Multiple Ip Adresses

Mesut Muhammet Şahin mmessah at gmail.com
Wed Apr 26 15:57:04 UTC 2017 

Hi,

Our Dhcp servers are running with failover. We make relay for ip requests
over network device to dhcp servers. (1 relay device and 2 dhcp server) We
detect some mac addresses that have multiple ip addresses for same vlan.

I attached dhcp servers log in attachment for one mac address. How can
clients get different ip addresses for same vlan?

# VLAN
subnet 100.64.0.0 netmask 255.255.224.0 {
  option routers 100.64.0.1;
  pool {
    failover peer "dhcp-failover";
    allow members of "dhcp-opt-82";
    default-lease-time 9000;
    min-lease-time 9000;
    max-lease-time 9000;
    range 100.64.0.41 100.64.31.250;
  }
}

Thanks in advance,

-- Mesut Muhammet Şahin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20170426/f5f447cc/attachment-0001.html>
-------------- next part --------------
Apr 26 09:05:01 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 09:05:01 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:05:01 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.14.231 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:05:01 dhcp_server_1 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:13:43 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:13:43 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:13:43 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.14.231 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:13:43 dhcp_server_1 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:36:56 dhcp_server_1 dhcpd: uid lease 100.64.14.231 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 09:36:56 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 09:36:58 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 09:36:58 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:26 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:26 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:01:44 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:01:44 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:09 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:09 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:09 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:09 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:13 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:13 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:39:18 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:39:18 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:09 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:09 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:12 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:12 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:54:11 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:54:11 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:06 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:06 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:11 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:11 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:19 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:19 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:58:32 dhcp_server_1 dhcpd: uid lease 100.64.30.97 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 10:58:32 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 10:58:32 dhcp_server_1 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:27:21 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:27:21 dhcp_server_1 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:26 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:26 dhcp_server_1 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:31 dhcp_server_1 dhcpd: uid lease 100.64.14.231 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 11:36:31 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.6.122 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 11:36:46 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.6.122 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 11:36:46 dhcp_server_1 dhcpd: DHCPACK on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:03 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:03 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:06 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:06 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:15 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:15 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:04:20 dhcp_server_1 dhcpd: uid lease 100.64.6.122 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:04:20 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 12:04:20 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:27 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.6.122 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 12:11:27 dhcp_server_1 dhcpd: DHCPACK on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:31 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:31 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:31 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.6.122 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:31 dhcp_server_1 dhcpd: DHCPACK on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:12:31 dhcp_server_1 dhcpd: uid lease 100.64.6.122 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:12:31 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 12:12:31 dhcp_server_1 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:31:11 dhcp_server_1 dhcpd: uid lease 100.64.6.122 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:31:11 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 12:31:11 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:31:14 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:31:14 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:06:06 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:06:06 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:24 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:24 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:26 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:26 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:28 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:28 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:32 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:32 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.144) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:45 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.144) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:45 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:00 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:00 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:02 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:02 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:16 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:16 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:33 dhcp_server_1 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:33 dhcp_server_1 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:41 dhcp_server_1 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:41 dhcp_server_1 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
-------------- next part --------------
Apr 26 09:05:01 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 via 100.64.0.23: load balance to peer failover-partner
Apr 26 09:05:01 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.14.231 (10.35.92.143) from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 09:13:43 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 via 100.64.0.23: load balance to peer failover-partner
Apr 26 09:13:43 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.14.231 (10.35.92.143) from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 09:13:43 dhcp_server_2 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:36:56 dhcp_server_2 dhcpd: uid lease 100.64.14.231 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 09:36:56 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 09:36:56 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:36:58 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:36:58 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 09:37:00 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:26 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23: load balance to peer failover-partner
Apr 26 10:00:30 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:00:30 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:01:44 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:01:44 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:09 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23: load balance to peer failover-partner
Apr 26 10:02:09 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:09 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:13 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:02:13 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:39:18 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:39:18 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:09 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:09 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:12 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:40:12 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:54:11 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:54:11 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:06 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23: load balance to peer failover-partner
Apr 26 10:57:11 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:11 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:19 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:57:19 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 10:58:32 dhcp_server_2 dhcpd: uid lease 100.64.30.97 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 10:58:32 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 11:27:21 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 11:27:21 dhcp_server_2 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:26 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:26 dhcp_server_2 dhcpd: DHCPACK on 100.64.14.231 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:31 dhcp_server_2 dhcpd: uid lease 100.64.14.231 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 11:36:31 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.6.122 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 11:36:31 dhcp_server_2 dhcpd: DHCPACK on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:46 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.6.122 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:36:46 dhcp_server_2 dhcpd: DHCPACK on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:03 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23: load balance to peer failover-partner
Apr 26 11:50:06 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23: load balance to peer failover-partner
Apr 26 11:50:15 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 11:50:15 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:04:20 dhcp_server_2 dhcpd: uid lease 100.64.6.122 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:04:20 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 12:11:27 dhcp_server_2 dhcpd: uid lease 100.64.30.97 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:11:27 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.6.122 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 12:11:31 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 12:11:31 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:31 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.6.122 (10.35.92.143) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:11:31 dhcp_server_2 dhcpd: DHCPACK on 100.64.6.122 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 12:12:31 dhcp_server_2 dhcpd: uid lease 100.64.6.122 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:12:31 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.14.231 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 12:31:11 dhcp_server_2 dhcpd: uid lease 100.64.14.231 for client 9c:2a:83:69:a9:99 is duplicate on 100.64.0.0/19
Apr 26 12:31:11 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23: lease owned by peer
Apr 26 12:31:14 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 via 100.64.0.23
Apr 26 12:31:14 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:06:06 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:06:06 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:24 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:24 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:26 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:26 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:28 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:28 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:32 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:32 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.144) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:41 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:45 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 (10.35.92.144) from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:37:45 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:00 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:00 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:02 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:02 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:16 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:16 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:33 dhcp_server_2 dhcpd: DHCPREQUEST for 100.64.30.97 from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:33 dhcp_server_2 dhcpd: DHCPACK on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:41 dhcp_server_2 dhcpd: DHCPDISCOVER from 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23
Apr 26 13:38:41 dhcp_server_2 dhcpd: DHCPOFFER on 100.64.30.97 to 9c:2a:83:69:a9:99 (android-e9e96a3d00fa2604) via 100.64.0.23

More information about the dhcp-users mailing list