From: Martijn Lievaart <m@rtij.nl>
To: Mike <1100100@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: NAT PREROUTING vs. filter FORWARD
Date: Sat, 21 Oct 2006 08:46:31 +0200 [thread overview]
Message-ID: <4539C247.9020803@rtij.nl> (raw)
In-Reply-To: <8ca422820610201004w4fe2091bnbdb4fbba7a0b5b6@mail.gmail.com>
Mike wrote:
> Martijn,
> The sciprt idea sounds quite clever and efficient!
> I would be very interested to see your method by script, if it is not
> a security risk, etc.
> Thank you very much for your response and idea.
It is pretty efficient. I write my firewall rules in perl. The loader
executes this script and pipes the output into iptables-restore. It is
not in a stage that I want to release it to the world yet, however.
M4
prev parent reply other threads:[~2006-10-21 6:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 18:25 NAT PREROUTING vs. filter FORWARD Mike
2006-10-19 18:27 ` Mike
2006-10-20 5:32 ` Jasbir Khehra
2006-10-20 13:36 ` Mike
2006-10-20 15:14 ` Martijn Lievaart
[not found] ` <4429765974127559812@unknownmsgid>
2006-10-20 17:04 ` Mike
2006-10-21 6:46 ` Martijn Lievaart [this message]
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=4539C247.9020803@rtij.nl \
--to=m@rtij.nl \
--cc=1100100@gmail.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