As the summary says, the Dhcp6Client issues an IPAddress.setAddress() even when
the address has just been renewed, rather than when it has been potentially
changed. Depending on the application, this can result in a lot of unnecessary
work being performed (such as re-registration upstream, etc).
The attached (trivial) patch changes the Dhcp6Client to not (re)set the IP
address in response to RENEW confirmations - by definition the address cannot
have changed at this point.
Original issue reported on code.google.com by jmatts...@dius.com.au on 16 Sep 2011 at 1:07
Original issue reported on code.google.com by
jmatts...@dius.com.au
on 16 Sep 2011 at 1:07Attachments: