It's not from the original system, but one exibiting the exact same sympyoms:
1. Client with problem (one of our many iOS devices)
DHCP: Server msg received, fip=ANY, fport=0 on MOBILE interface
DHCPD: DHCPDISCOVER received from client 016c.c26b.293b.89 on interface MOBILE.
DHCPD: send ping pkt to 10.10.15.205
DHCPD: ping got no response for ip: 10.10.15.205
DHCPD: Add binding 10.10.15.205 to radix tree
DHCPD: Binding successfully added to hash table
DHCPD: Sending DHCPOFFER to client 016c.c26b.293b.89 (10.10.15.205).
DHCPD: client requests option 3.
DHCPD: copy option 3 (length = 4) to outgoing message.
DHCPD: client requests option 6.
DHCPD: copy option 6 (length = 8) to outgoing message.
DHCPD: Total # of raw options copied to outgoing DHCP message is 2.
DHCPD: creating ARP entry (10.10.15.205, 6cc2.6b29.3b89).
DHCPD: unicasting BOOTREPLY to client 6cc2.6b29.3b89 (10.10.15.205).
DHCPD: Binding successfully deactivated
dhcpd_destroy_binding() removing NP rule for client 10.10.15.205
DHCPD: free ddns info and binding
DHCP: Server msg received, fip=ANY, fport=0 on MOBILE interface
DHCPD: DHCPREQUEST received from client 016c.c26b.293b.89.
DHCPD: Extracting client address from the message
DHCPD: State = DHCPS_REBOOTING
DHCPD: State = DHCPS_REQUESTING
DHCPD: Client 016c.c26b.293b.89 specified it's address 10.10.15.205
DHCPD: Client is on the correct network
DHCPD: requested address 10.10.15.205 not found
DHCPD: Sending DHCPNAK to client 016c.c26b.293b.89.
DHCPD: broadcasting BOOTREPLY to client 6cc2.6b29.3b89.
2. Client without problem:
DHCP: Server msg received, fip=ANY, fport=0 on MOBILE interface
DHCPD: DHCPDISCOVER received from client 01bc.cfcc.736c.0e on interface MOBILE.
DHCPD: send ping pkt to 10.10.15.156
DHCPD: ping got no response for ip: 10.10.15.156
DHCPD: Add binding 10.10.15.156 to radix tree
DHCPD: Binding successfully added to hash table
DHCPD: Sending DHCPOFFER to client 01bc.cfcc.736c.0e (10.10.15.156).
DHCPD: client requests option 3.
DHCPD: copy option 3 (length = 4) to outgoing message.
DHCPD: client requests option 6.
DHCPD: copy option 6 (length = 8) to outgoing message.
DHCPD: Total # of raw options copied to outgoing DHCP message is 2.
DHCPD: creating ARP entry (10.10.15.156, bccf.cc73.6c0e).
DHCPD: unicasting BOOTREPLY to client bccf.cc73.6c0e (10.10.15.156).
DHCP: Server msg received, fip=ANY, fport=0 on MOBILE interface
DHCPD: DHCPREQUEST received from client 01bc.cfcc.736c.0e.
DHCPD: Extracting client address from the message
DHCPD: State = DHCPS_REBOOTING
DHCPD: State = DHCPS_REQUESTING
DHCPD: Client 01bc.cfcc.736c.0e specified it's address 10.10.15.156
DHCPD: Client is on the correct network
DHCPD: Client accepted our offer
DHCPD: Client and server agree on address 10.10.15.156
DHCPD: Renewing client 01bc.cfcc.736c.0e lease
DHCPD: Client lease can be renewed
DHCPD: Sending DHCPACK to client 01bc.cfcc.736c.0e (10.10.15.156).
DHCPD: Including FQDN option name 'Windows-Phone.MOBILE.ro' rcode1=0, rcode2=0 flags=0x0
DHCPD: client requests option 3.
DHCPD: copy option 3 (length = 4) to outgoing message.
DHCPD: client requests option 6.
DHCPD: copy option 6 (length = 8) to outgoing message.
DHCPD: Total # of raw options copied to outgoing DHCP message is 2.
DHCPD: creating ARP entry (10.10.15.156, bccf.cc73.6c0e).
DHCPD: unicasting BOOTREPLY to client bccf.cc73.6c0e (10.10.15.156).
As far as i can tell, DHCP leases for iOS devices are immidiately destroyed upon sending the DHCPOFFER packet. No idea why.
.png "Antonio Simoes"){kind=avatar}
