From: Patrick McHardy <kaber@trash.net>
To: Grant Taylor <gtaylor@riverviewtech.net>
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>, seandarcy2@gmail.com
Subject: Re: why can't I DNAT SIP?
Date: Fri, 09 May 2008 16:23:58 +0200 [thread overview]
Message-ID: <48245E7E.8080206@trash.net> (raw)
In-Reply-To: <48245C6B.1090506@riverviewtech.net>
Grant Taylor wrote:
> On 05/08/08 17:24, sean darcy wrote:
>> I tried it both ways. FWIW, it works both ways for iax. I showed it
>> that way because the LOG statement were that way. I've run them all
>> both ways.
>>
>> Yeah, but why is iptables not filtering the packet correctly; it's
>> just a port 5060 udp packet. How can it matter that it's 5060 instead
>> of 4569?
>
> With out knowing the full scenario, I can't say for sure. Are you
> dealing with an on going established connection, thus one that is not
> passing through the NAT chain again?
>
> Is it possible that you are dealing with SIP Reinvited traffic that
> really has a source of elsewhere?
>
> More things are starting to come in to play.
Some questions that might help answering this:
- Which kernel version are you running?
- What helpers are loaded (both NAT and conntrack)
- How does the entry from /proc/net/nf_conntrack for the
SIP connection look like?
next prev parent reply other threads:[~2008-05-09 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 1:10 why can't I DNAT SIP? sean darcy
2008-05-08 19:31 ` Grant Taylor
2008-05-08 22:24 ` sean darcy
2008-05-09 1:18 ` sean darcy
2008-05-09 14:15 ` Grant Taylor
2008-05-09 14:23 ` Patrick McHardy [this message]
2008-05-10 2:04 ` sean darcy
2008-05-10 8:43 ` Jan Engelhardt
2008-05-11 14:53 ` sean darcy
2008-05-11 14:58 ` Jan Engelhardt
2008-05-11 18:02 ` sean darcy
2008-05-11 18:12 ` Jan Engelhardt
2008-05-12 16:01 ` Patrick McHardy
2008-05-09 0:31 ` Mike Wright
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=48245E7E.8080206@trash.net \
--to=kaber@trash.net \
--cc=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.org \
--cc=seandarcy2@gmail.com \
/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.