Right before the ACK, a random UDP broadcast arrives which occupies the only slot in the RawSocket buffer. When the ACK arrives, the RawSocket is full, so it doesn't accept the packet. smoltcp then replies with a "port unreachable". This probably shouldn't happen.
(DHCP doesn't retry the request after that and the device goes offline, but I think that's another bug...)
Right before the ACK, a random UDP broadcast arrives which occupies the only slot in the RawSocket buffer. When the ACK arrives, the RawSocket is full, so it doesn't accept the packet. smoltcp then replies with a "port unreachable". This probably shouldn't happen.
(DHCP doesn't retry the request after that and the device goes offline, but I think that's another bug...)