Hello Andrew:

We had slated to address this issue in our upcoming 4.4.0 release under a another ticket, rt16171, which complained of the same problem.  Apparently, we lost track of the fact that this issue was solved under rt19660 by adding a parameter, intitial-delay <time> to the dhclient configuration file.

You may have already discovered this parameter, if so please disregard.  If not, hopefully this is still of some use to you.

Regards,

Thomas Markwalder
ISC Software Engineering