From nobody Wed Jun 12 11:28:38 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VzjwW38SSz5M2yS for ; Wed, 12 Jun 2024 11:28:43 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VzjwW0hjQz4sLr; Wed, 12 Jun 2024 11:28:40 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 5FE37892F8; Wed, 12 Jun 2024 11:28:38 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.18.1/8.16.1) with ESMTPS id 45CBScsd010456 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 12 Jun 2024 11:28:38 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 45CBScQ1010455; Wed, 12 Jun 2024 11:28:38 GMT (envelope-from phk) Message-Id: <202406121128.45CBScQ1010455@critter.freebsd.dk> To: Michael Gmelin cc: Ronald Klop , current@freebsd.org Subject: Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out In-reply-to: <20240612125217.68483cf9.grembo@freebsd.org> From: "Poul-Henning Kamp" References: <202406120747.45C7lRGZ009491@critter.freebsd.dk> <413984193.6719.1718185609109@localhost> <202406121039.45CAdal6010274@critter.freebsd.dk> <20240612125217.68483cf9.grembo@freebsd.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10453.1718191718.1@critter.freebsd.dk> Date: Wed, 12 Jun 2024 11:28:38 +0000 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Queue-Id: 4VzjwW0hjQz4sLr -------- Michael Gmelin writes: > You can do an interface route hack I think you misunderstand the situation. We are talking about people who have /etc/rc.conf files which relied on how default netmasks have worked for nearly three decades, Now that we have changed that default, many of them will see a single line rapidly scroll off their console, and a set of very bewilding symptoms of DNS not working correctly. The solution is not for them to apply some weird, complex and unnecessary interface configuration. The solution is for us to not break their configuration in the first place, or at least make it much more obvious to them, where the problem is to be found. Defaulting to a /8 netmask for 192.168.x.y does not make *any* sense ever. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.