From: Nick Pasich <NewsLetters@NickAndBarb.net>
To: Madison Kelly <linux@alteeve.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Looking for an editable script
Date: Thu, 29 Jan 2004 18:16:15 -0800 [thread overview]
Message-ID: <20040130021615.GA32006@66.27.62.2> (raw)
Madison,
You might want to try Arno's iptables firewall.
It has a lot of features and can be tweaked to fit your needs.
Arno's iptables firewall - Single- & multi-homed firewall script with DSL/ADSL
s(C) Copyright 2001-2003 by Arno van Amersfoort
Homepage : http://rocky.molphys.leidenuniv.nl/
Freshmeat homepage : http://freshmeat.net/projects/iptables-firewall/?topic_id=151
---( Nick Pasich )---
> Date: Thu, 29 Jan 2004 12:02:03 -0500
> From: Madison Kelly <linux@alteeve.com>
> To: netfilter@lists.netfilter.org
> Subject: Looking for an editable script
>
> Hi all,
>
> I am trying to build a script to serve my office network. To date I
> have used Monmotha's Firewall script but I need more than it provides. I
> have been trying to hack his excellent script to fit my needs but a
> programmer I am not! :)
>
> I need something I can work into doing the following;
>
> - Allow limited TCP/UDP ports into the firewall/router (easy enough)
> - Allow limited TCP/UDP ports into LAN clients (common list for all LAN
> clients)
> - NAT clients that will be public and for each client allow a specific
> list of inbound TCP/UDP ports and where the clients will, internally,
> have their own subnet seperate from the LAN clients.
>
> I am not asking anyone to do my work, but a head start would be
> greatly appreciated! In the meantime, back to trying to bang Monmotha's
> script to suite (please save me!) ;)
>
> Madison
next reply other threads:[~2004-01-30 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 2:16 Nick Pasich [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-29 17:02 Looking for an editable script Madison Kelly
2004-01-30 2:49 ` Tom Eastep
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040130021615.GA32006@66.27.62.2 \
--to=newsletters@nickandbarb.net \
--cc=linux@alteeve.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox