After the Dhcp6Client has received an ADVERTISE message, it records the server
address and transitions its state into send-request. However, it doesn't
actually send the request message until the next 15sec interval comes around.
This means that it takes at least 15sec to obtain an address, despite the fact
that the Dhcp6Client won't accept any further ADVERTISE messages in the
meantime.
As the client has already made its server decision as soon as it receives the
first ADVERTISE, the attached trivial patch lowers the time-to-request to one
second (minimum permitted by RFC 3315).
Original issue reported on code.google.com by jmatts...@dius.com.au on 16 Sep 2011 at 1:15
Original issue reported on code.google.com by
jmatts...@dius.com.au
on 16 Sep 2011 at 1:15Attachments: