Yeah. It didn't make any sense... so I've been going through all the DHCP fields today, and I think I found one interesting problem. It's not in the stack we thought it was, at least not in the first place :) Connman DHCP (both client and server) seems to have an endianness bug with the dhcp server id (option 54). The data never seems to go through htonl/ntohl even though other IP addresses (e.g. "requested IP") do. I'm not qualified to comment on whether the Netgear device should be using option 54 for anything, but if my understanding is correct this would explain so much... I showed a tcpdump to Jukka Rissanen and he seemed to agree it's probably a connman bug. Tomasz, can you check this -- should be easy to reproduce: either run connman dhcp server and look at bootp messages in tcpdump, or just use the client and print out the server id somewhere in the code. Jussi