From: KOVACS Krisztian <hidden@balabit.hu>
To: netfilter-devel@lists.netfilter.org
Cc: Dmitry <dg@ipcb.net>
Subject: Re: Symmetric NAT for udp
Date: Thu, 17 Nov 2005 13:34:11 +0100 [thread overview]
Message-ID: <200511171334.12015@nienna> (raw)
In-Reply-To: <437C70F5.2090401@ipcb.net>
Hi,
On Thursday 17 November 2005 13.00, Dmitry wrote:
> Hi all - i have a trouble with making netfilter nat act like symmetric
> for udp . Normally for udp it acts like port restricted cone nat ( the
> main feature is that it doesnt mangle src port if several udp packets
> come from same src ip/port - to different dest. In case of tcp it acts
> like symmetric nat - ie each syn packet even from same src ip/port cause
> src port mangling. What i need is to make it act like symmetric for udp
> too. So i just looked throught udp/tcp specific files
> (conntrack_proto_udp, nat_proto_udp and relative tcp ) and didnt find
> anything that makes it work different for tcp and udp. Tests revealed
> that at first time (and after timeout) each udp packets (even from same
> src port/ip but to diff dest ) cause new conntrack creation. But when
> it checkes before postrouting is tuple taken - for same src/port
> somehow it says that no - so mangling doesnt occur. Can somebody give me
> a hint where to dig?
Dmitry, you don't even mention the exact version number of the kernel
you're testing. Could you tell us that precious information?
By the way, it would help a _lot_ if you could write nfsim testcases
demonstrating the problem (the difference between TCP and UDP) you're
seeing. Would that be possible?
--
Regards,
Krisztian Kovacs
next prev parent reply other threads:[~2005-11-17 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 12:00 Symmetric NAT for udp Dmitry
2005-11-17 12:34 ` KOVACS Krisztian [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-17 15:37 Dmitry
2005-11-17 11:51 Dmitry
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=200511171334.12015@nienna \
--to=hidden@balabit.hu \
--cc=dg@ipcb.net \
--cc=netfilter-devel@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.