Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!pacbell.com!iggy.GW.Vitalink.COM!riscit.NOC.Vitalink.COM!ejm
From: ejm@riscit.NOC.Vitalink.COM (Erik J. Murrey)
Newsgroups: news.software.nntp
Subject: Re: The News on Mac vs NNTP
Keywords: The News Mac NNTP
Message-ID: <1991May3.150203.21059@iggy.GW.Vitalink.COM>
Date: 3 May 91 15:02:03 GMT
References: <1991May3.020349.23317@unlinfo.unl.edu> <heal.673238650@mrcnext.cso.uiuc.edu> <1991May3.130444.26161@unlinfo.unl.edu>
Sender: usenet@iggy.GW.Vitalink.COM (USENET News Admin)
Distribution: na
Organization: Vitalink Communications, Fremont, California
Lines: 28
Nntp-Posting-Host: riscit.noc.vitalink.com

In article <1991May3.130444.26161@unlinfo.unl.edu>, mosemann@sardion.unl.edu (Russell Mosemann) writes:
|> 
|>    If at all possible, I would prefer not to enter around 600 IP numbers
|> into our name server.  Is there a way to convince NNTP that IP numbers
|> are OK?


( You might get a flood of these answeres, but... )

Sure,

If you define your class A,B, or C address in /etc/networks, then simply
put the network name in your nntp_access file.  For instance, at Vitalink,
we have our class-B (132.240) in /etc/networks:
vita-net	132.240

And in nntp_access:
vita-net	read	post

This allows any 132.240.x.x machine read/posting access to the news.


'Hope this is what you need!

---
Erik J. Murrey
Vitalink Communications NOC
ejm@NOC.Vitalink.COM	...!uunet!NOC.Vitalink.COM!ejm