Jen Linkova <furry13@xxxxxxxxx> wrote:
> - check if making host a dual-stack solves the issue (either by moving
> the host to a dual-stack segment or by changing DHCPv4 client config)
I think, if the DHCPv4-server can be told to selectively ignore the
dhc-v6only option for that host, that we can make it dual-stack without
touching the client config.
The host would think it's on a network that doesn't offer IPv6-only.
So I think that the option makes troubleshooting easier :-)
> If an engineer is not willing to diagnose such a complex issue they
> are welcome to configure their DHCP servers so they do not respond
> with the option.
> Problem solved.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
