From: Alexandre Moore <alexandre.j.moore@gmail.com>
To: netfilter@vger.kernel.org
Subject: [Kernel 2.6.26][rtp/rtcp]
Date: Mon, 16 Jan 2012 11:40:17 +0100 [thread overview]
Message-ID: <4F13FE91.1070205@gmail.com> (raw)
Hello there,
I am currently working on a linux kernel 2.6.26 box with linked to
multiple ISP (so one or more ethernet connections) and specific ones for
VoIP usage.
What i want is to restrict SIP rtp/rtcp to specific interfaces
(load-balance) and I can only use iptables rules kernel modules or hack
the kernel itself (for resource purposes).
My problem is that I have two different servers for sip rtp (port 5060)
and sip rtcp (random port 10k+).
So when the rtcp connection is established, it is not related/expected
to the rtp and I can't track it with iptables. (callback
ip_nat_sip_expected in net/ipv4/netfilter/nf_nat_sip.c is not called).
box ----- > rtp server xxx.xxx.xxx.1
\-----> rtcp server xxx.xxx.xxx.2
I am doing it wrong ?
Is there a kernel module that I missed ?
is this kind of trivia is dealt differently with more recent kernels ?
(maybe i can convince my boss to upgrade).
Regards.
(French IT dev here, so sorry if english is a bit awkward).
--
Alexandre Moore
http://alexandremoore.com
reply other threads:[~2012-01-16 10:40 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=4F13FE91.1070205@gmail.com \
--to=alexandre.j.moore@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.