From: Kerin Millar <kerframil@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Help tweaking asterisk rules
Date: Sun, 04 Mar 2012 04:39:32 +0000 [thread overview]
Message-ID: <jiurm5$m0i$1@dough.gmane.org> (raw)
In-Reply-To: <450EB7580E6AE7469F8826BFBF09BAB6761D15@earwax.uent.com>
On 21/01/2011 02:05, Max DiOrio wrote:
> I was also hoping someone can provide some guidance on leaving the RTP
> ports UDP 10000:20000 open to all IP's on the WAN. What type of
> security issue will this raise? Should I install Fail2Ban in this
> setup? The only issue I have with Fail2Ban was that it blocked my
> access from the LAN within 15 seconds of it coming online.
They needn't be open at all. Instead, load the the ip_conntrack_sip
module and ensure that your iptables policy is stateful.
http://www.iptel.org/sipalg/
Using fail2ban carelessly might pave the way for remotely exploitable
DoS attacks. Though it has its uses, I wouldn't generally recommend it.
http://www.ossec.net/main/attacking-log-analysis-tools
Cheers,
--Kerin
next prev parent reply other threads:[~2012-03-04 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 2:05 Help tweaking asterisk rules Max DiOrio
2012-03-04 4:39 ` Kerin Millar [this message]
2012-03-04 7:10 ` Jan Engelhardt
2012-03-04 7:25 ` Kerin Millar
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='jiurm5$m0i$1@dough.gmane.org' \
--to=kerframil@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