Re: [SLUG] ipfwadm

2001-02-19 Thread Terry Collins
Paul Robinson wrote: Hi guys, I've been trying to get my head around some old rulesets for ipfwadm as I slug archives -- Terry Collins {:-)}}} Ph(02) 4627 2186 Fax(02) 4628 7861 email: [EMAIL PROTECTED] www: http://www.woa.com.au WOA Computer Services lan/wan,

RE: [SLUG] ipfwadm

2001-02-19 Thread Paul Robinson
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

Re: [SLUG] ipfwadm

2001-02-19 Thread marty
I've been trying to get my head around some old rulesets for ipfwadm as I want to add the feature of forwarding everything sent to say 8088 on my firewall to a particular machine inside my network 192.168.0.2 you want "port forwarding" not "forwarding" * you'll need ipmasqadm (google

Re: [SLUG] ipfwadm

2001-02-19 Thread Darrell Burkey
I purchased Robert L. Ziegler's "Linux Firewalls" book and highly recommend it. He also has a tool on his web site that writes rules after prompting you for info. Not sure how well it works but the web site is fantastic for info about packet firewalls. Have a look at:

RE: [SLUG] ipfwadm

2001-02-19 Thread Marty Richards
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