I do not think that a way similar to IPv4's DHCP keyword in rc.conf works for DHCPv6 because DHCPv6 has several cases including invocation of DHC by RA or not, stateful or stateless, and IA_NA and/or IA_PD. A typical case is combination of RA for the default router and DHCPv6 for other information. In this case, it is expected in our implementation that DHCPv6 is initiated by rtsold(8) after processing RA. If a system had this patch and an ifconfig line in rc.conf had "DHCP6", DHCP client would be invoked multiple times. Another typical example which many ISPs offer is combination of RA and IA_NA for the uplink interface and IA_PD for the LAN interface. Both will not work well with the "DHCP6" keyword.

I think we can go ahead with this, too.

No objection from me. Thank you for your good work!

Looks reasonable to add notification when ia6_flags is changed, but why is RTM_ADD used instead of RTM_CHANGE? rt_addrmsg() is for addition/removal of an address and RTM_ADD is translated to RTM_NEWADDR there.

It builds with no problem.

I am still reviewing this and your NAT64 patch and probably I will be able to get back on Monday.

I think removing the ioctl including the symbol makes sense after doing an exp-run of package build as ae@ pointed out.

Thanks, looks good to me.

Sorry for the delay. Looks good to me.

In D6626#140434, @ed wrote:

In D6626#140418, @hrs wrote:

Looks good to me. Do we need strdup(), BTW? I think FreeBSD's basename() does not change
memory area where name points though SUS says it may be changed.

My plan is to switch over to the POSIX prototype in 12.0-CURRENT. ;-)

Looks good to me. Do we need strdup(), BTW? I think FreeBSD's basename() does not change
memory area where name points though SUS says it may be changed.

I think this is definitely the way to go. Thank you for your work!

Excellent! Thank you for your work. I will review and test it.