dhcpcd-discuss

Hi Guy

On Saturday 03 September 2016 13:05:09 Guy Yur wrote:
> Tested with VirutalBox, 2 cpu cores and em0 interface.
> dhcpcd trunk 018576c771 unpatched.
> FreeBSD 10.3 and head r305297.
> 
> 1. kernel with D5469 as only networking change.
> 2. kernel with no networking changes.
> 
> 1. IPv6 EUI64 link local and EUI64 ULA configured before dhcpcd starts.
> dhcpcd adding "slaac private" ULA and global from RA.
> 2. No preconfigured addresses.
> dhcpcd adding "slaac private" link local, ULA and global from RA.
> 
> IPv4 and IPv6 addresses added by dhcpcd are removed on link disconnect
> or "if down" in all scenarios above.
> IPv4 and IPv6 addresses are restored on link disconnect/reconnect
> for all scenarios above.
> IPv4 address is restored on "if down/if up" for all scenarios.
> IPv6 addresses are restored on "if down/if up" if the kernel has D5469.
> IPv6 addresses are restored on "if down/if up" when the kernel
> doesn't have D5469 only if no preconfigured link local and ULA.

I finally got some time to install a fresh FreeBSD-10.3 amd64 QEMU image on my 
Linux dev box (so no patches) and fixed dhcpcd in all the above scenarios.

The basic fix was to reset the internal address flags on carrier up and when 
starting IPv6 check the address flag for the LL address and if tentative start 
the address polling mechanism as we have for the other flags.

So basically try a new dhcpcd trunk please as I put some other patches in too.

Fingers crossed, dhcpcd should now be fine for all your scenarios!
Let me know and if success a new release will be soon :)

Roy