From: sean darcy <seandarcy2@gmail.com>
To: netfilter@vger.kernel.org
Subject: does -p udp --dport 5060 not work with -j LOG?
Date: Wed, 30 Apr 2008 18:27:43 -0400 [thread overview]
Message-ID: <fvarov$iq2$1@ger.gmane.org> (raw)
I'm trying to figure out why my sip port forwarding doesn't work.
$IPT -t nat -A PREROUTING -i external -p udp --dport 5060 -j DNAT --to
10.10.10.180:5060
$IPT -A FORWARD -p udp -m state --state NEW -d 10.10.10.180 --dport 5060
-j ACCEPT
So before everything I put:
$IPT -t nat -A PREROUTING -i external -p udp --sport 5060 --dport 5060
-j LOG --log-prefix "SIP-BEFORE: "
(I also tried it without --sport.)
But in syslog I get packets both from "lan" my internal interface:
SIP-BEFORE: IN=lan OUT= MAC=01:00:5e:7f:ff:fa:00:15:99:25:e1:32:08:00
SRC=10.10.10.102 DST=239.255.255.250 LEN=364 TOS=0x00 PREC=0x00 TTL=1
ID=33785 PROTO=UDP SPT=1024 DPT=1900 LEN=344
SIP-BEFORE: IN=lan OUT= MAC=01:00:5e:7f:ff:fa:00:15:99:25:e1:32:08:00
SRC=10.10.10.102 DST=239.255.255.250 LEN=372 TOS=0x00 PREC=0x00 TTL=1
ID=33795 PROTO=UDP SPT=1024 DPT=1900 LEN=352
And, from the external interface, it logs all udp ports:
SIP-BEFORE: IN=external OUT=
MAC=00:48:54:8b:ab:29:00:1a:e2:84:bf:3b:08:00 SRC=xxx.yyy.113.22
DST=xxx.yyy.167.178 LEN=126 TOS=0x04 PREC=0x00 TTL=112 ID=56357
PROTO=UDP SPT=17214 DPT=32375 LEN=106
SIP-BEFORE: IN=external OUT=
MAC=00:48:54:8b:ab:29:00:1a:e2:84:bf:3b:08:00 SRC=xxx.yyy.113.22
DST=xx.yy.167.178 LEN=126 TOS=0x04 PREC=0x00 TTL=112 ID=56357 PROTO=UDP
SPT=17214 DPT=32375 LEN=106
So any suggestions on port forwarding sip appreciated. I'm disappointed
I can't figure this out myself using -j LOG (:
sean
next reply other threads:[~2008-04-30 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 22:27 sean darcy [this message]
2008-05-01 3:23 ` does -p udp --dport 5060 not work with -j LOG? Diego Lacerda
2008-05-01 23:36 ` sean darcy
2008-05-01 23:53 ` Steven Kath
2008-05-02 0:45 ` Diego Lacerda
2008-05-02 1:10 ` sean darcy
2008-05-02 1:40 ` Steven Kath
2008-05-02 13:34 ` Jan Engelhardt
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='fvarov$iq2$1@ger.gmane.org' \
--to=seandarcy2@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.