Subject: Re: ypbind -broadcast/ypserv broken
To: Brian C. Grayson <email@example.com>
From: Bill Studenmund <firstname.lastname@example.org>
Date: 08/14/1998 21:10:26
On Fri, 14 Aug 1998, Brian C. Grayson wrote:
> We use /var/yp/pdslab.acl, and run ypserv -d -a /var/yp/pdslab.acl.
> Here's the entire pdslab.acl file, including a stale comment:
> ## For now, allow marvin, and deny all others.
> allow host orac.ece.utexas.edu
> allow host localhost
> allow host marvin
> allow host r2d2
> allow host c3p0
> allow host orac
> allow host data
> allow host lore
> allow host sim1
> allow host sim2
> allow host sim3
> allow host sim4
> allow host sim5
> allow host sim6
> allow host hal
> deny all
> All of the machines work if I specify the server in
> /var/yp/binding/pdslab.ypservers (so I know the ACL works
> overall). Is there some special flag that says, handle bcast
> requests from any of the allowable hosts?
Is there a particular reason you are using the broadcast option?
> Does anyone have the non-explicit/bcast method working? Is it
> some weird ACL vs. securenet thing?
> I also should have mentioned that we aren't quite at
> cutting-edge current: the server's kernel is from June 29, and
> ypserv is from June 11. But a quick check of ypserv's source
> files shows only localhostname.c and yplog.c (both in common/)
> have been changed since our build.
I can't seem to find any reference to broadcasting in the ypserver, other
than that it's not recomended to run a -broadcast client...