Date: Wed, 12 Jun 2024 11:28:38 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Michael Gmelin <grembo@freebsd.org> Cc: Ronald Klop <ronald-lists@klop.ws>, current@freebsd.org Subject: Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out Message-ID: <202406121128.45CBScQ1010455@critter.freebsd.dk> In-Reply-To: <20240612125217.68483cf9.grembo@freebsd.org> References: <202406120747.45C7lRGZ009491@critter.freebsd.dk> <413984193.6719.1718185609109@localhost> <202406121039.45CAdal6010274@critter.freebsd.dk> <20240612125217.68483cf9.grembo@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202406121128.45CBScQ1010455>