On 2019-02-15, Stephen P. Molnar <s.mol...@sbcglobal.net> wrote: > > On 02/15/2019 12:11 PM, Felix Miata wrote: >> Reco composed on 2019-02-15 19:48 (UTC+0300): >> >>> On Fri, Feb 15, 2019 at 11:17:06AM -0500, Felix Miata wrote: >>>> I made ipv6.disable=1 a standard option here at least as far back as 2011. >>>> If it ever caused a >>>> problem I never found out about it. >>> That's a fine example of "works for me" approach. >>> And I've seen multiple cases where "disable IPv6" equaled "non-booting OS". >> Maybe I left out an important point, which is that "for me" means hundreds >> of installations >> including most of the historically most popular distros, Debian, *buntu, >> Mint, Fedora, openSUSE, >> Mageia, Gentoo and a few others. >> >> I have a hard time imagining a dependency on ipv6 to be able to boot, even >> including thin client or >> PXE, but then I don't know anything of any prospect of booting from outside >> a firewall where ipv6 >> might be a sole option. > Thanks for all of the responses. > > I elected to go with; > > echo 'net.ipv6.conf.all.disable_ipv6 = 1' > /etc/sysctl.d/noipv6.conf > > which did, indeed, result in the file being created. > > However, there is only one problem, it didn't work. >
I did see an (Ubuntu?) bug to that exact effect (maybe not at all pertinent, in which case, sorry). https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771222
