separating readers and peers
rra at stanford.edu
Sun Apr 9 18:10:54 UTC 2006
Christian Kratzer <ck-lists at cksoft.de> writes:
> were are running a single innd with both readers and
> peers on the same machine and have separated them to
> different ips.
> We would now like for stats purposes to enforce that
> readers connect to the reader ip and peers can only
> connect to the other ip but can't seem to do this with
> a single inn.
> What we would ideally like to do is set noreaders
> in innd and only bind our feeder ip in the inn.
> We would then like to run something that binds
> our reader ip and forks the nnrpds.
> Ayn ideas ?
You've pretty much outlined the solution. To implement that in INN, set
noreader in inn.conf and set bindaddress to the IP address you want to use
for peers. Then, run nnrpd from an inetd equivalent that supports setting
the bind address, and bind it to the other IP address. In the past, I've
used tcpserver (from <http://cr.yp.to/ucspi-tcp.html> for this, but I
expect xinetd will work just as well.
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
More information about the inn-workers