From debbugs-submit-bounces@debbugs.gnu.org Sat May 14 15:10:04 2022 Received: (at 55335) by debbugs.gnu.org; 14 May 2022 19:10:04 +0000 Received: from localhost ([127.0.0.1]:47520 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1npx9Q-0002O9-5M for submit@debbugs.gnu.org; Sat, 14 May 2022 15:10:04 -0400 Received: from minsky.hcoop.net ([104.248.1.95]:42418) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1npx9O-0002NW-6W for 55335@debbugs.gnu.org; Sat, 14 May 2022 15:10:02 -0400 Received: from marsh.hcoop.net ([45.55.52.66]) by minsky.hcoop.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1npx9H-0002rA-R6; Sat, 14 May 2022 15:09:55 -0400 Date: Sat, 14 May 2022 15:09:55 -0400 (EDT) From: Jack Hill X-X-Sender: jackhill@marsh.hcoop.net To: =?ISO-8859-15?Q?Ludovic_Court=E8s?= Subject: Re: bug#55335: openssh-service no longer listens on IPv6 In-Reply-To: <87lev4f71w.fsf_-_@gnu.org> Message-ID: References: <87r153q913.fsf@cbaines.net> <20220513142312.21382-1-mail@cbaines.net> <87lev4f71w.fsf_-_@gnu.org> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="925712948-1546090832-1652555395=:11587" X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 55335 Cc: Christopher Baines , 55335@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --925712948-1546090832-1652555395=:11587 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Sat, 14 May 2022, Ludovic Courtès wrote: > Hi, > > Thinking about it, what do you think is the risk of using AF_INET6 > unconditionally? > > AFAICS it just works. Is there a switch somewhere that might affect > that behavior? Yes, I beleive that it's in sysctl: ``` $ sysctl net.ipv6.bindv6only net.ipv6.bindv6only = 0 ``` If enabled, the v6 socket wouldn't work for v4. Disabled is the default on Guix System. I don't know what would happen if v6 were disabled entirely. Hopefully that's not something we have to worry about in 2022. HTH, Jack --925712948-1546090832-1652555395=:11587--