From: sean darcy <seandarcy2@gmail.com>
To: netfilter@vger.kernel.org
Subject: where are my udp packets going?
Date: Sat, 15 Nov 2008 16:04:41 -0500 [thread overview]
Message-ID: <gfndh9$n0s$1@ger.gmane.org> (raw)
I'm trying to setup port forwarding for a VOIP server that uses IAX
packets, port 4569:
+ /sbin/iptables -t nat -A PREROUTING -i eth0 -p udp --dport 4569 -j
DNAT --to 10.10.10.180:4569
+ /sbin/iptables -A FORWARD -p udp -m state --state NEW -d 10.10.10.180
--dport 4569 -j ACCEPT
but the packets aren't showing up at 10.10.10.180.
I put in a bunch of log statements:
$IPT -t raw -A PREROUTING -i $EXTIF -p udp --dport 4569 -j LOG
--log-prefix "iax packet RAW: "
$IPT -t nat -A PREROUTING -i $EXTIF -p udp --dport 4569 -j DNAT --to
10.10.10.180:4569
$IPT -t nat -A PREROUTING -i $EXTIF -p udp --dport 4569 -j LOG
--log-prefix "iax packet PRE NAT: "
$IPT -A FORWARD -p udp -m state --state NEW -d 10.10.10.180 --dport 4569
-j ACCEPT
$IPT -A FORWARD -p udp --dport 4569 -d 10.10.10.180 -j LOG
--log-prefix "iax packet FORWARD: "
$IPT -t nat -A POSTROUTING -p udp --dport 4569 -j LOG
--log-prefix "iax packet POST: "
So, I would expect each iax packet to show up sequentially as:
iax packet RAW:
iax packet PRE NAT:
iax packet FORWARD:
iax packet POST:
But no:
I get lots of "iax packet RAW: " , and an "iax packet FORWARD: "
every 2 - 10 "iax packet RAW: " messages. That's it. no postrouting,
no prerouting nat.
And the voip server sees no iax packets.
Where are they going?
sean
next reply other threads:[~2008-11-15 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 21:04 sean darcy [this message]
2008-11-15 23:54 ` where are my udp packets going? sean darcy
2008-11-16 16:01 ` Pascal Hambourg
2008-11-16 21:31 ` sean darcy
2008-11-17 10:28 ` Pascal Hambourg
2008-11-17 16:49 ` sean darcy
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='gfndh9$n0s$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.