Hi Paul,
Yeah, its easy ;)
rinetd works well with ipchains/ipfw - the input and output chains/rules are
definately still enforced. The forwarding rules are also enforced, but its
rare I use a forward rule to block traffic accross the rinetd portfw - I
usually use an input rule to control access to the forwarded port on the
external interface.
Cheers,
Marty
On Tuesday, February 20, 2001 7:24 AM, Paul Robinson
[SMTP:[EMAIL PROTECTED]] wrote:
> Thanks Marty,
> When you said it was really easy I thought "sure sure" but that
> was amazingly easy to setup and write out rules for, installed and
> configured in about 3 mins and that's including downloading and reading
the
> README and man file. From reading through the man file, and could not find
> any mention of how it interacts with other software such as ipfwadm or
> ipchains. What happens if you deny something in one program and then allow
> it in the other? Does it let it through or does the program that is
denying
> the particular connection stop it when it is it's turn to filter the
> packets? I only ask because easy to install usually means easy to
circumvent.
>
> Terry, I'd checked the slug archives already and couldn't find any
articles
> that addressed this problem (just lots of hits on articles saying "you
> could use ipfwadm"). Thanks anyway.
>
> Paul
> At 12:36 AM 20/02/2001 +1100, you wrote:
> >Hi Paul,
> >
> >Have you met rinetd? Its a really easy way of portforwarding without
using
> >ipfw or ipchains. I have a copy available for download at
> >www.netwaynetworks.com.au/files/linux/rinetd_tar.tar
> >
> >Cheers,
> >Marty
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
