In article <31E4EC06 .
fr>, zwobada @
(Jean-Francois Zwobada) wrote:
> Hi Stefan,
> You're absolutely right, this is way you can do if you want
> different news servers available for different internal clients.
> With the Gauntlet, if you omit the "-plug-to" option, every address
> declared in the 'source field' is able to connect to everywhere. It is
> not true with the toolkit, unfortunately.
> With the toolkit, you should consider listening on a different port
> for every external server you want to contact. But it seems that
> news clients don't want to connect to something different from 119...
> plug-gw: port nntp1 mynet.* -plug-to 1external.news.server -port nntp
> plug-gw: port nntp2 mynet.* -plug-to 2external.news.server -port nntp
Sorry about reviving a ?dead? thread... just got back from vacation. On
our news server, I use the plug-gw to bring all incoming feeds into our
internal news server. To feed the external news servers, I connect to
different ports (1191, 1192, 1193, ...) I then modified several programs
in INN (innxmit, nntpsend, news.daily, etc...) to add a -P option to
specify the remote port. This way, I can maintain any number of
bidirectional news feeds through the firewall. As you point out though, I
can not tell who a connection is coming from. The only indication to this
is the /var/log/news/news file and the headers of the actual articles.
Steve Waltner | Steve .
Symbios Logic | Phone: (316) 636-8498
3718 N. Rock Road | FAX: (316) 636-8889
Wichita, KS 67226 |