Well, as is often the case, user error added some confusion here.
My system (and possibly kirkland and ttx) have a second dhcp server available on the network. That dhcp server was responding, and sometimes its response was being accepted rather than that of the CC.
So, user error causes the '400' timeout, but the original debugging shown above showed empty data fields and a 200 response. As far as I can tell, that is still valid.
Additionally, I belive I've got the correct dnsmasq/dd-wrt configuration options to ignore the UEC nodes:
dhcp-host=d0:0d:*:*:*:*,ignore
Well, as is often the case, user error added some confusion here.
My system (and possibly kirkland and ttx) have a second dhcp server available on the network. That dhcp server was responding, and sometimes its response was being accepted rather than that of the CC.
So, user error causes the '400' timeout, but the original debugging shown above showed empty data fields and a 200 response. As far as I can tell, that is still valid.
Additionally, I belive I've got the correct dnsmasq/dd-wrt configuration options to ignore the UEC nodes: host=d0: 0d:*:*: *:*,ignore
dhcp-