From: Mr Ritter <netfilter@candlefire.org>
To: netfilter@lists.netfilter.org
Subject: packets missing/skipping DNAT rules
Date: Tue, 28 Mar 2006 15:34:20 -0700 [thread overview]
Message-ID: <4429B9EC.8030200@candlefire.org> (raw)
I have some basic rules in the PREROUTING of *nat that perform a DNAT
like so:
-A PREROUTING -p tcp --dport 1234 -j DNAT --to 1.2.3.4
However, on a pretty consistent basis this rule fails to be applied and
I'll see the results of that in the kernel logs like:
Mar 28 15:24:21 hostname IN=eth1 OUT= MAC=<mac addrs> SRC=w.x.y.z
DST=4.3.2.1 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=37514 DF PROTO=TCP
SPT=3232 DPT=1234 WINDOW=0 RES=0x00 ACK RST URGP=0
The log shows that a small sampling of packets did not apply the DNAT,
and it is happening enough to notice, I'd say 1 in 100.
Any suggestions on how to troubleshoot and resolve this?
I'm not trying to do anything real fancy, its a simple dual NIC
interface, eth0 is private and eth1 public.
TIA
--
Ritter
reply other threads:[~2006-03-28 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4429B9EC.8030200@candlefire.org \
--to=netfilter@candlefire.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox