From: Kerin Millar <kerframil@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Help tweaking asterisk rules
Date: Sun, 04 Mar 2012 07:25:56 +0000 [thread overview]
Message-ID: <jiv5e5$98q$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1203040810190.1405@frira.zrqbmnf.qr>
On 04/03/2012 07:10, Jan Engelhardt wrote:
> On Sunday 2012-03-04 05:39, Kerin Millar wrote:
>
>> 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/
>
> This is all outdated material. It's nf_conntrack_sip and has been long
> merged into the kernel already.
I am aware that it exists in the mainline kernel. Thank you for pointing
out that I got the name wrong. I managed asterisk in my prior job and
did actually use nf_conntrack_sip so I should have recalled the
distinction. Nevertheless, I think that the page still serves as a
useful intro to those unfamiliar with the sip connection tracking
module. At least, it did for me when I was facing the same issue as how
to gracefully handle SIP.
Cheers,
--Kerin
prev parent reply other threads:[~2012-03-04 7:25 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
2012-03-04 7:10 ` Jan Engelhardt
2012-03-04 7:25 ` Kerin Millar [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='jiv5e5$98q$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.