From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: netfilter@vger.kernel.org
Subject: DNAT working for one host but not another
Date: Sun, 04 Dec 2016 14:01:41 -0500 [thread overview]
Message-ID: <1480878101.19944.29.camel@interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
I have a DNAT rule on a host who's purpose is to redirect traffic that
is destined for port 23768 to port 5060 on that host:
Chain PREROUTING (policy ACCEPT 7340K packets, 362M bytes)
pkts bytes target prot opt in out source destination
9 3878 DNAT udp -- enp1s7 * 0.0.0.0/0 0.0.0.0/0 udp dpt:23768 to::5060
That rule seems to be working for one host but not another. This is
what I end up with in the conntrack table:
udp 17 29 src=10.75.22.8 dst=10.75.23.212 sport=5060 dport=6060 [UNREPLIED] src=10.75.23.212 dst=10.75.22.8 sport=6060 dport=5060 mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1
udp 17 175 src=10.75.22.200 dst=10.75.22.8 sport=6060 dport=23768 src=10.75.22.8 dst=10.75.22.200 sport=5060 dport=6060 [ASSURED] mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1
udp 17 29 src=10.75.23.212 dst=10.75.22.8 sport=6060 dport=23768 [UNREPLIED] src=10.75.22.8 dst=10.75.23.212 sport=5060 dport=1024 mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1
So as you can see, 10.75.22.200 seems to be properly natted and moves
to the ASSURED state but the natting for 10.75.23.212 seems to get
confused and we end up with two of UNREPLIED entries.
Any idea what I'm doing wrong, or what is going wrong?
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2016-12-04 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 19:01 Brian J. Murrell [this message]
2016-12-04 19:06 ` DNAT working for one host but not another Brian J. Murrell
2016-12-05 7:04 ` Llorente Santos Jesus
2016-12-05 14:43 ` Brian J. Murrell
2016-12-05 15:52 ` Humberto Jucá
2016-12-05 15:56 ` Brian J. Murrell
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=1480878101.19944.29.camel@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox