Hi Thomas, We did the switch from IPv4-only to IPv6-only a while ago and I can really recommend to take baby-steps to test the waters. PREFER_IPV4 = false on a few machines is a good way to get started while having a safety net; things will fall back to IPv4 gracefully most of the time - that is, if your network setup isnât entirely borked and daemons just wait ages for timeouts. Still, I recommend an extra baby-step in-between: use condor_ping with disabled IPv4 (works nicely via environment variables) to check that the daemons can communicate via IPv6. Cheers, Max > On 19. Feb 2024, at 17:20, Thomas Hartmann <thomas.hartmann@xxxxxxx> wrote: > > Hi all, > > not a critical issue more out of curiosity, but I just noticed, that due to the default > PREFER_IPV4 = true > the daemons all still prefer IPv4 on our dual-stack clusters. > > Now, with preparing a cluster revamp in progress, I am curious if there are any points in embracing IPv6 and switch PREFER_IPV4 to false...? > > Cheers, > Thomas > _______________________________________________ > HTCondor-users mailing list > To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a > subject: Unsubscribe > You can also unsubscribe by visiting > https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users > > The archives can be found at: > https://lists.cs.wisc.edu/archive/htcondor-users/
Attachment:
smime.p7s
Description: S/MIME cryptographic signature