Removing the sysctl should be very pretty safe as far as ports goes (I did wonder if thing s might read the sysctl and change behaviour but it seems that's not the case). Looks like only nsh will break from doing that and it's easily fixed.
I did a search for things using the ioctl too. It looks like probably everything that listens with dual sockets uses it. On 18 May 2016 06:48:06 BST, Damien Miller <[email protected]> wrote: >On Tue, 17 May 2016, Henning Brauer wrote: > >> > What about systems with net.inet6.ip6.v6only=0? >> >> Those haven't been taken into consideration by yours truly and might >be >> the compelling argument to have this code :) > >That sysctl isn't hooked up to anything, it should be removed. >(compare IPV6CTL_VARS against IPV6CTL_NAMES in in6.h) > >-d -- Sent from a phone, please excuse the formatting.
