06:21:27.531866 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 70:f1:a1:03:9f:12, length 300
06:21:27.545151 arp who-has 172.16.221.88 tell 172.16.0.2
06:21:27.579052 arp who-has 172.16.0.4 tell 172.16.0.122
06:21:27.625232 arp who-has 172.16.0.2 (00:13:d3:ce:29:94) tell 172.16.221.87
06:21:27.625240 arp reply 172.16.0.2 is-at 00:13:d3:ce:29:94
06:21:27.716473 arp who-has 172.16.221.59 tell 172.16.0.1
06:21:27.762426 IP 172.16.6.60.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 00:1a:2a:98:5c:7e, length 300
06:21:27.809513 IP 172.16.0.2.67 > 172.16.6.60.68: BOOTP/DHCP, Reply, length 302
06:21:27.847296 IP 172.16.1.125.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 00:22:3f:a3:a5:e3, length 552
06:21:27.884687 IP 172.16.0.2.67 > 172.16.1.125.68: BOOTP/DHCP, Reply, length 302
06:21:28.000435 IP 172.16.0.2.67 > 172.16.221.88.68: BOOTP/DHCP, Reply, length 319
06:21:28.006709 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 70:f1:a1:03:9f:12, length 320
06:21:28.105156 arp who-has 172.16.0.4 tell 172.16.0.2
06:21:28.244190 IP 172.16.0.2.67 > 172.16.221.88.68: BOOTP/DHCP, Reply, length 336
06:21:28.310258 IP 172.16.4.41.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 00:1d:19:de:95:3a, length 300
06:21:28.352429 IP 172.16.0.2.67 > 172.16.4.41.68: BOOTP/DHCP, Reply, length 302
06:21:28.456663 arp who-has 172.16.6.136 tell 172.16.0.1
06:21:28.489145 arp who-has 172.16.221.88 tell 0.0.0.0
06:21:28.545145 arp who-has 172.16.221.88 tell 172.16.0.2
06:21:28.556482 arp reply 172.16.221.88 is-at 70:f1:a1:03:9f:12
06:21:28.588998 arp who-has 172.16.0.4 tell 172.16.0.122
06:21:29.105145 arp who-has 172.16.0.4 tell 172.16.0.2
06:21:29.202161 IP 172.16.6.244.68 > 172.16.0.2.67: BOOTP/DHCP, Request from c0:3f:0e:68:be:b9, length 548
06:21:29.205151 arp who-has 172.16.0.162 tell 172.16.0.2
06:21:29.205229 arp reply 172.16.0.162 is-at 00:0f:ea:15:83:af
06:21:29.205704 arp reply 172.16.0.162 is-at 00:0f:ea:15:83:af
06:21:29.206287 arp reply 172.16.0.162 is-at 00:0f:ea:15:83:af
06:21:29.243397 IP 172.16.0.2.67 > 172.16.6.244.68: BOOTP/DHCP, Reply, length 308
06:21:29.244435 arp who-has 172.16.6.244 tell 0.0.0.0
06:21:29.455346 IP 172.16.221.119.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 00:11:11:22:47:89, length 307
06:21:29.456548 arp who-has 172.16.6.136 tell 172.16.0.1
06:21:29.486526 arp who-has 172.16.221.88 tell 0.0.0.0
06:21:29.501496 IP 172.16.0.2.67 > 172.16.221.119.68: BOOTP/DHCP, Reply, length 334
06:21:29.589027 arp who-has 172.16.0.4 tell 172.16.0.122
06:21:29.750195 IP 172.16.0.167.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 00:08:7b:09:23:94, length 548
06:21:29.750445 IP 172.16.0.2.67 > 172.16.0.167.68: BOOTP/DHCP, Reply, length 324
06:21:29.776522 arp who-has 172.16.221.59 tell 172.16.0.1
06:21:30.062309 IP 172.16.221.34.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 60:33:4b:cc:bc:65, length 300
06:21:30.085145 arp who-has 172.16.6.253 tell 172.16.0.2
06:21:30.085771 arp reply 172.16.6.253 is-at 00:16:cf:c8:d6:d8
06:21:30.088619 arp reply 172.16.6.253 is-at 00:16:cf:c8:d6:d8
06:21:30.089168 arp reply 172.16.6.253 is-at 00:16:cf:c8:d6:d8
06:21:30.105145 arp who-has 172.16.0.4 tell 172.16.0.2
06:21:30.110118 IP 172.16.0.2.67 > 172.16.221.34.68: BOOTP/DHCP, Reply, length 302
06:21:30.193341 arp who-has 172.16.221.88 (70:f1:a1:03:9f:12) tell 0.0.0.0
06:21:30.215143 arp who-has 172.16.221.118 tell 172.16.0.2
06:21:30.215750 arp reply 172.16.221.118 is-at 00:26:b0:81:11:8f
06:21:30.217582 arp reply 172.16.221.118 is-at 00:26:b0:81:11:8f
06:21:30.218140 arp reply 172.16.221.118 is-at 00:26:b0:81:11:8f
06:21:30.325632 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 70:f1:a1:03:9f:12, length 300
06:21:30.471129 IP 172.16.6.111.68 > 172.16.0.2.67: BOOTP/DHCP, Request from 00:21:cc:41:8f:ec, length 306
06:21:30.589127 arp who-has 172.16.0.4 tell 172.16.0.122
06:21:30.737147 IP 172.16.0.2.67 > 172.16.6.111.68: BOOTP/DHCP, Reply, length 335
06:21:30.776509 arp who-has 172.16.221.59 tell 172.16.0.1
06:21:31.194511 arp who-has 172.16.221.88 (70:f1:a1:03:9f:12) tell 0.0.0.0
