From: "ml@bortal.de" <ml@bortal.de>
To: netfilter@vger.kernel.org
Subject: Replace Switch with Firewall - Is there some auto-learnign tool for firewall requirements?
Date: Wed, 14 Nov 2007 14:10:48 +0100 [thread overview]
Message-ID: <473AF3D8.1040204@bortal.de> (raw)
Hello List,
right now we have a "flat"-network (one subnet):
192.168.0.1-100 and 192.168.0.101-254
Those two Network segments are connected by a bridged linux box. Not
filtering at this point. Its just a switch really.
Now we would like to keep the "flat"-network for some good reasons and
replace the linux-bridge with a bridged firewall (physdev match).
Since i dont want to break the network with its functionality i thought
of capturing the current traffic for some time and check out the IPs,
Ports, etc... which are beeing used.
Like the learning mode grsecurity has.
Based on the captured information i would like to create my firewall
rule with firewallbuilder.
I know i have to check out the captured rules well to make sure i dont
implement a hole in my firewall setup!
Is there a way or project to capture my firewall requirements? I guess i
basically need all SYN-Flags and its DEST-Ports?
How can i get them easily out the the massive traffic each day? Do you
need more infos?
Any ideas are welcome!
Thanks, Mario
reply other threads:[~2007-11-14 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=473AF3D8.1040204@bortal.de \
--to=ml@bortal.de \
--cc=netfilter@vger.kernel.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