Hi Allyn, > I have a situation where I am working on a network with a very slow DHCP > response (~1min). > > We're seeing that connman autoassigns an IP on boot, but never retries to get > a new IP. If we restart connman via pkill -HUP connmand && > /usr/sbin/connmand -W nl80211,wext then connman picks up the assigned ip > (shown via list-services), but does not update ifconfig > > I'm wondering if there is a way to increase the dhcp wait/timeout value to > account for this very long delay. > > Or if there is any particular reason that connman seems to ignore the new IP > after it should have received it...
I leave this for the other to dissect in detail, but essentially if a DHCP response takes too long, then at some point we are just going ahead with a link-local address. However if some time later we finally get a DHCP response, we should upgrade our link-local to the DHCP provided address. This might be a bug here in our handling. Maybe we are not trying hard enough to continue with DHCP. But as I said, I leave some others to dissect this. However, your DHCP server is seriously bad. No idea how in these day and age, anybody can have such a bad server ;) Regards Marcel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
