Lewis G Rosenthal wrote:

My NetWare servers handle DHCP on my networks, so I leave the DHCP server turned off in the routers/AP's. XWLAN has no problem getting an address, as all it does is start the DHCPCD, anyway.

Yes, and no, it really fires of a dhcpstrt command! just launching the client deamon would not do that.

If there's a problem getting parameters, I'd suggest bumping up the timeout setting for DHCPCD; it may just be a lazy DHCP server.

I assume you mean the timeout parameter for the DHCPSTRT command.

If so I think you may misunderstand this parameter  -it only tells how long dhcpstrt should wait for a response of dhcpcd. XWLAN (of course) does not use it, but sets it to zero, because for an event driven GUI it is useless to block the own program like this. Instead, the DHCPCD will try it anyway, no matter if and how long dhcpstrt will wait for a response.

XWLAN also waits forever, but uses its own "GUI app method", showing the "configuration status" bitmap as long as the IP interface did not get configured, what is checked about every 200ms. Until that (or until the dhcpcd is killed or stopped), the daemon repeats the DHCP RECOVER command again and again (you can determine the period by activating the log - see dhcpcd.cfg  for details). Having said all that, no parameter change will stop that or even improve anything.