I just noticed that a machine we were testing on here was getting an address conflict, in that it was being assigned an addr from DHCP, but someone else had statically assigned it.
In this instance, nwamd seemed to just keep looping telling me there was a DHCP timeout, and still waiting for an addr. The GUI kept popping up a notification too, not good either. So I'm wondering about how we're handling this case. It would make sense that nwamd should really know that DHCP sees a dup address - it does seem to acknowledge it as such in the logs - and after several tries, enter a state where it flags this to the user. The GUI could then react appropriately, telling the user so they can look into it - the actual address being assigned is also useful here too, and it does look like NWAM gets it according to the show-events output, but then it's rejected. What do people think? Darren.
