From: Patrick McHardy <kaber@trash.net>
To: Huy Vu Pham <markoflinux@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: SIP NAT CONTRACK Module with Netfilter in kernel 2.4.x
Date: Sat, 04 Mar 2006 10:04:53 +0100 [thread overview]
Message-ID: <44095835.7010703@trash.net> (raw)
In-Reply-To: <cb81d4010603020312q3309cd70w27fd5862744eb09f@mail.gmail.com>
Huy Vu Pham wrote:
> Dear Netfilter Devel list,
> I got problem very strange with Netfilter in linux kernel 2.4.x.
>
> I apply contrack/nat SIP protocol
> (http://openwrt.alphacore.net/patches/buildroot/317-netfilter-nat-sip
> ) with HELPER module to capture all RTP packets.
> (
> #Out from WAN site: eth1
> iptables -t mangle -A POSTROUTING -o eth1 -p UDP -m helper --helper
> sipd00 -j MARK --set-mark 0x20
> #Out from LAN site: eth0
> iptables -t mangle -A POSTROUTING -o eth0 -p UDP -m helper --helper
> sipd00 -j MARK --set-mark 0x21
> )
>
> My test case like this:
> SIP PHONE A (Outside NAT) ----- NAT BOX (Have SIP ALG) ------- SIP
> PHONE B (Inside NAT).
>
> 1. Reboot NAT BOX, A call B. SIP MODULE can capture all RTP packets,
> Before RTP timeout, I make the call from B to A also OK.
>
> 2. Reboot NAT BOX, B call A. SIP MODULE "CAN NOT" capture any RTP packets.
> Before RTP timeout, I make the call from A to B also got the same problem.
>
> What is difference between case (1) and case(2)?
The SIP helper currently only tracks one direction. I wanted to fix
it for some time, but didn't get to it yet.
prev parent reply other threads:[~2006-03-04 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cb81d4010603020310x1f865d2dhf14088682952108@mail.gmail.com>
2006-03-02 11:12 ` SIP NAT CONTRACK Module with Netfilter in kernel 2.4.x Huy Vu Pham
2006-03-04 9:04 ` Patrick McHardy [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=44095835.7010703@trash.net \
--to=kaber@trash.net \
--cc=markoflinux@gmail.com \
--cc=netfilter-devel@lists.netfilter.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.