From: carlopmart <carlopmart@gmail.com>
To: netfilter@vger.kernel.org
Subject: Recommended iptables setup for management servers
Date: Mon, 30 Apr 2012 20:59:00 +0200 [thread overview]
Message-ID: <4F9EE0F4.30302@gmail.com> (raw)
Hi all,
I am searching some tutorials about how to configure a robust/lockdown
iptables rules to protect management servers (for example some NSM
servers and firewall management servers).
Yes, exists a lot of info in the web but nothing pretty much concise.
I have used over several years BSD firewalls (pf) and this task is very
simple ... but with iptables I am really lost ...
The best tutorial that I have found is:
http://www.remetter.de/os_linux_skript.php
.. but it seems too old, or not? My linux servers are CentOS 6 ...
My primary objective is to block malformed packets, scans, and control
packets managed by mangle. Some of these servers have two interfaces and
some services needs to be reached by this secondary interface.
Any help?
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
next reply other threads:[~2012-04-30 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 18:59 carlopmart [this message]
2012-05-01 12:48 ` Recommended iptables setup for management servers Giles Coochey
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=4F9EE0F4.30302@gmail.com \
--to=carlopmart@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).