netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Indrek Paas <indrekpaas@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Iptables and voip (sip) traffic
Date: Sun, 11 Apr 2010 12:07:09 +0300	[thread overview]
Message-ID: <l2q596a60ad1004110207w394a042dn1a1fc12853158539@mail.gmail.com> (raw)
In-Reply-To: <4BC0BCF3.5080302@bofhland.org>

On Sat, Apr 10, 2010 at 9:01 PM, whiplash <whiplash@bofhland.org> wrote:
> Indrek Paas ha scritto:
>> Hi,
>>
>> I have searched information about iptables and Sip protocol used for
>> Voip calls. I remember that this particular protocol had problems
>> passing firewalls which were configured to use NAT.
> [...]
>> And voip service provider claims that the Linux router should be
>> switched to their Thompson device. Because iptables "interferes with
>> their service". So any help and information is greatly appreciated.
>
> Linux kernel already has two modules for handling natting and conntracking
> of SIP protocol, nf_nat_sip and nf_conntrack_sip; your VoIP service
> provider is trying to sell you something you don't really need, possibly.
>
> HTH.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

So there is no need for special Iptables rules to manage sip protocol?
Other than allowing the traffic for port 5060? If this is true then I can ask
the provider to look over the settings for voip account.


Indrek P.

      reply	other threads:[~2010-04-11  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 13:53 Iptables and voip (sip) traffic Indrek Paas
2010-04-10 18:01 ` whiplash
2010-04-11  9:07   ` Indrek Paas [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=l2q596a60ad1004110207w394a042dn1a1fc12853158539@mail.gmail.com \
    --to=indrekpaas@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).