Date: Fri, 28 Jun 2002 00:20:03 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/39896: netmask 0xffffff00 no longer works in /etc/exports Message-ID: <200206280720.g5S7K3UN051964@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/39896; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: "Crist J. Clark" <crist.clark@attbi.com> Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/39896: netmask 0xffffff00 no longer works in /etc/exports Date: Fri, 28 Jun 2002 17:11:58 +1000 (EST) On Thu, 27 Jun 2002, Crist J. Clark wrote: > On Thu, Jun 27, 2002 at 11:21:15AM -0700, Jin Guojun[DSD] wrote: > [snip] > > OK, I _can_ reproduce this. There is something really, really wack > going on. This is actually the issue I thought you were refering to > when I first read your PR. > > Your error is here, > > > eubie# echo "/data -network 131.243.2 -mask 255.255.255.0" > /etc/exports > ^ > As I understand inet_network(3), you are refering to the network, > > 131.243.0.2 > > And if you change that to, > > 131.243.2.0 > > Everything in all of your examples should work fine. This should be > trivial to do in your scripting, so I think you have the correction you > need for your problem. The conventions for export(5) are quite different from those of inet_network(3). 131.243.2 means all hosts on the subnetwork 131.243.2. I know very little about this except that the TIRPC changes broke the convention for -network, and rev.1.48 of mountd.c or thereabouts fixed this. I noticed the breakage for -network but didn't noticed any problems for -mask. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206280720.g5S7K3UN051964>