<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Use netstat to list listening ports on the box (netstat -ln) and see if it shows up as tcp6 or tcp. On our (older) 17.11.8 server:<div class=""><br class=""></div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">$ netstat -ln | grep :6817</div><div class="">tcp 0 0 0.0.0.0:6817 0.0.0.0:* LISTEN </div><div class=""><br class=""></div><div class="">$ nc -6 :: 6817<br class="">Ncat: Connection refused.</div><div class=""><br class=""></div><div class="">$ nc -4 localhost 6817<br class="">^C<br class=""><br class=""></div></blockquote><div class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><br class=""><blockquote type="cite" class="">On May 1, 2020, at 12:44 , William Brown <<a href="mailto:william@signalbox.org.uk" class="">william@signalbox.org.uk</a>> wrote:<br class=""><br class="">For some services that display of 0.0.0.0 does include IPv6, although it is counter-intuitive. Try to see if you can connect to it using the IPv6 address.<br class=""><br class="">William<br class=""><br class="">On Fri, 1 May 2020 at 16:35, Thomas Schäfer <<a href="mailto:thomas@cis.uni-muenchen.de" class="">thomas@cis.uni-muenchen.de</a>> wrote:<br class="">Hi,<br class=""><br class="">is there an switch, option, environment variable, configurable key word to <br class="">enable IP6 for the slurmd and slurmctld daemons?<br class=""><br class="">tcp LISTEN 0.0.0.0:6818<br class=""><br class="">isn't a good choice, were everything else (nfs, ssh, ntp, dns) runs over IPv6.<br class=""><br class="">Regards,<br class="">Thomas<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class=""></blockquote><br class=""></div></div></body></html>