Date: Thu, 12 Feb 2015 09:53:15 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: Warren Block <wblock@wonkity.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: RE: Invalid subnet masks Message-ID: <a2e4143bb6fe4f128bfa638afce4637e@SERVER.ad.usd-group.com> In-Reply-To: <20150212000434.GA15127@over-yonder.net> References: <7e069c1946454793b1c7e0be988877c4@SERVER.ad.usd-group.com> <alpine.BSF.2.11.1502111033140.4693@wonkity.com> <CCB57DE0-24A4-4A06-ADB9-776B2000EE70@userve.net> <20150212000434.GA15127@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wed, Feb 11, 2015 at 05:49:35PM +0000 I heard the voice of Matt Church= yard, and lo! it spake thus: > > > On 11 Feb 2015, at 17:38, Warren Block <wblock@wonkity.com> wrote: > > > ifconfig em0 inet 192.168.1.1/24 > >=20 > > Yeah I've been using that format in rc.conf for years. Quicker to type= =20 > > and looks tidy. > Ditto. Though in the grand tradition of being given the inch and lusting= after the mile, it makes me grumpy seeing the dotted-quad netmask in 'ifco= nfig' output, making me have to work > to see if the > match and back-convert to add things. 8-} It's actually hex format in ifconfig unless I'm missing something ;)=20 The discussion on -hackers linked earlier in this thread was actually a con= versation about changing the output to dotted quad, then it moved on to pro= viding a switch to allow users to specify dotted quad or CIDR notation. Obv= iously it was never implemented although you don't really want to mess with= the output of established core commands unless there's good reason.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a2e4143bb6fe4f128bfa638afce4637e>