Okay, I am seeing something very weird. I a standalone IAP (no other IAP on the network) with a DHCP server running on it: 192.168.22.x subnet.
Client is wired to the network and is turned on (has the WLAN interface turned on at the same time as the ETH interface).
I see a DHCP exchange on the AP and the client recieves the address of 192.168.22.228 (timestamp of Feb 15 11:00:21 2017)
Feb 15 11:00:21 2017 192.168.4.30 <192.168.4.30 F0:5C:19:C2:AE:36> dnsmasq-dhcp[14413]: DHCPACK(br0) 192.168.22.228 00:0e:8e:38:5d:aa E0027
Feb 15 11:00:21 2017 192.168.4.30 <192.168.4.30 F0:5C:19:C2:AE:36> dnsmasq[14413]: dhcp_reply 1485: magic vlan user add (0 192.168.22.228 00:0e:8e:38:5d:aa 1 18 0.0.0.0 0.0.0.0 255.255.255.0)
However, the client table (show clients via the CLI) shows an IP address of 0.0.0.0 (still on the wire)
The client is removed from the wired connection at Feb 15 11:01:08 (client logs), but is unreachable as it has a 0.0.0.0 IP address.
We let the client sit for a few minutes and then reboot the client at Feb 15 11:04:55 2017. The AP logs shows the client dissociating as expected.
When the client reconnects, we see another successful DHCP exchange, but this time the user IP address gets properly written. Now the "show clients" table properly shows an IP address of 192.168.22.228
Feb 15 11:05:10 2017 192.168.4.30 <192.168.4.30 F0:5C:19:C2:AE:36> dnsmasq-dhcp[14413]: DHCPACK(br0) 192.168.22.228 00:0e:8e:38:5d:aa E0027
Feb 15 11:05:10 2017 192.168.4.30 <192.168.4.30 F0:5C:19:C2:AE:36> dnsmasq[14413]: dhcp_reply 1485: magic vlan user add (0 192.168.22.228 00:0e:8e:38:5d:aa 1 18 0.0.0.0 0.0.0.0 255.255.255.0)
Feb 15 11:05:17 2017 192.168.4.30 stm[3395]: <304008> <DBUG> <192.168.4.30 F0:5C:19:C2:AE:36> |ap| user ip:192.168.22.228 mac:00:0e:8e:38:5d:aa
Is there something up with the routing on the AP or Client side that affects whether a 0.0.0.0 address or the correct DHCP address is added to the client table based on if the client is also in a wired state?
Full logs related to the client are attached.