Re: Permanent Use of IPv4

2019-02-16 Thread Reco
Hi. On Fri, Feb 15, 2019 at 10:14:10PM +0100, Pascal Hambourg wrote: > Le 15/02/2019 à 17:48, Reco a écrit : > > > > Why it is safe - because systemd configures NICs first, starts services > > next, and then applies kernel knobs (aka sysctl). > > Are you sure ? AFAICS, sysctl is started

Re: Permanent Use of IPv4

2019-02-15 Thread Pascal Hambourg
Le 15/02/2019 à 16:13, Stephen P. Molnar a écrit : Thanks for help from this gropup I can force the use of IPv4 by running:  sysctl -w net.ipv6.conf.all.disable_ipv6=1. This does not force the use of IPv4 but disables the use of IPv6 addresses on existing interfaces. For a number of reasons

Re: Permanent Use of IPv4

2019-02-15 Thread Pascal Hambourg
Le 15/02/2019 à 17:48, Reco a écrit : Why it is safe - because systemd configures NICs first, starts services next, and then applies kernel knobs (aka sysctl). Are you sure ? AFAICS, sysctl is started before networking, and NICs may be configured asynchronously if they have allow-auto.

Re: Permanent Use of IPv4

2019-02-15 Thread Pascal Hambourg
Le 15/02/2019 à 20:03, Stephen P. Molnar a écrit : 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 cause

Re: Permanent Use of IPv4

2019-02-15 Thread David Wright
On Fri 15 Feb 2019 at 14:03:47 (-0500), Stephen P. Molnar 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 bac

Re: Permanent Use of IPv4

2019-02-15 Thread Curt
On 2019-02-15, Stephen P. Molnar 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 ev

Re: Permanent Use of IPv4

2019-02-15 Thread Stephen P. Molnar
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

Re: Permanent Use of IPv4

2019-02-15 Thread Felix Miata
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" appr

Re: Permanent Use of IPv4

2019-02-15 Thread Reco
Hi. On Fri, Feb 15, 2019 at 11:17:06AM -0500, Felix Miata wrote: > Reco composed on 2019-02-15 19:02 (UTC+0300): > > > On Fri, Feb 15, 2019 at 10:55:23AM -0500, Felix Miata wrote: > > >> To me, "on boot" implies something on the kernel cmdline, e.g.: > > >>ipv6.disable=1 > > > And

Re: Permanent Use of IPv4

2019-02-15 Thread Felix Miata
Reco composed on 2019-02-15 19:02 (UTC+0300): > On Fri, Feb 15, 2019 at 10:55:23AM -0500, Felix Miata wrote: >> To me, "on boot" implies something on the kernel cmdline, e.g.: >> ipv6.disable=1 > And by doing *this* you're risking breaking systemd and the overall > boot process. > Yep, the

Re: Permanent Use of IPv4

2019-02-15 Thread Reco
Hi. On Fri, Feb 15, 2019 at 10:55:23AM -0500, Felix Miata wrote: > Reco composed on 2019-02-15 18:23 (UTC+0300): > > > On Fri, Feb 15, 2019 at 10:13:14AM -0500, Stephen P. Molnar wrote: > > >> Thanks for help from this gropup I can force the use of IPv4 by running: > >> sysctl -w net.i

Re: Permanent Use of IPv4

2019-02-15 Thread Grzesiek Sójka
On 2/15/19 4:12 PM, Stephen P. Molnar wrote: Thanks for help from this gropup I can force the use of IPv4 by running:  sysctl -w net.ipv6.conf.all.disable_ipv6=1. If you would like to prevent the kernel from loading IPv6 simply add the following: ipv6.disable=1 to the kernel boot parameters.

Re: Permanent Use of IPv4

2019-02-15 Thread Felix Miata
Reco composed on 2019-02-15 18:23 (UTC+0300): > On Fri, Feb 15, 2019 at 10:13:14AM -0500, Stephen P. Molnar wrote: >> Thanks for help from this gropup I can force the use of IPv4 by running: >> sysctl -w net.ipv6.conf.all.disable_ipv6=1. > ... >> My question is how can I implement the sysctl st

Re: Permanent Use of IPv4

2019-02-15 Thread Grzesiek Sójka
On 2/15/19 4:12 PM, Stephen P. Molnar wrote: Thanks for help from this gropup I can force the use of IPv4 by running:  sysctl -w net.ipv6.conf.all.disable_ipv6=1. If you would like to prevent the kernel from loading IPv6 simply add the followink

Re: Permanent Use of IPv4

2019-02-15 Thread Bastien Durel
Le vendredi 15 février 2019 à 10:12 -0500, Stephen P. Molnar a écrit : > Thanks for help from this gropup I can force the use of IPv4 by > running: sysctl -w net.ipv6.conf.all.disable_ipv6=1. > > For a number of reasons I have just done a fresh install of Stretch, > hoping that the installer wo

Re: Permanent Use of IPv4

2019-02-15 Thread Reco
Hi. On Fri, Feb 15, 2019 at 10:13:14AM -0500, Stephen P. Molnar wrote: > Thanks for help from this gropup I can force the use of IPv4 by running: > sysctl -w net.ipv6.conf.all.disable_ipv6=1. ... > My question is how can I implement the sysctl statement on boot? echo 'net.ipv6.conf.all.