From: KOVACS Krisztian <hidden@sch.bme.hu>
To: netfilter@lists.netfilter.org
Cc: "Keserű Kornél" <keseruk@freemail.hu>
Subject: Re: lost UDP packets with matching NAT rules
Date: Tue, 14 Feb 2006 22:21:38 +0100 [thread overview]
Message-ID: <200602142221.39824@krak> (raw)
In-Reply-To: <freemail.20060114103405.20767@fm05.freemail.hu>
Hi,
On Tuesday 14 February 2006 10:34, Keserû Kornél wrote:
> I'm using iptables (v1.3.4 on a 2.6.15.3 kernel) in order to NAT
> incoming UDP packets arriving on a single IP:port (1-1 rules in PRE-
> and POSTROUTING chains in the nat table). I found out that packets are
Why do you need two rules here? Redirecting incoming UDP packets to a
single IP:port has nothing to do with POSTROUTING, it's a single rule on
PREROUTING.
> How could I find out, why are the packets lost? Is there a log entry
> somewhere that says if an UDP packet was dropped because of... ?
Try monitoring /proc/net/stat/ip_conntrack. I guess the number you find
in the insert_failed column will match the number of dropped packets.
--
KOVACS Krisztian
next prev parent reply other threads:[~2006-02-14 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 9:34 lost UDP packets with matching NAT rules Keserű Kornél
2006-02-14 21:21 ` KOVACS Krisztian [this message]
2006-02-15 13:18 ` Keserű Kornél
2006-02-15 15:15 ` KOVACS Krisztian
2006-02-15 17:16 ` Keserű Kornél
2006-02-17 9:43 ` KOVACS Krisztian
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=200602142221.39824@krak \
--to=hidden@sch.bme.hu \
--cc=keseruk@freemail.hu \
--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 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.