From: Martin Bangiev <martin.bangiev@borsabg.com>
To: netfilter@lists.netfilter.org
Subject: DNAT & SNAT delay
Date: Tue, 14 Jun 2005 12:13:37 +0300 [thread overview]
Message-ID: <42AE9FC1.6050204@borsabg.com> (raw)
Hi guys,
I have two applications based in different networks that has to
communicate with each other using many small UDP packets. Due to
security reasons I set the firewall for SNAT and DNAT dynamically. Here
is the exact situation.
Client1:
IP - 10.0.0.2
Client2:
IP - 172.16.0.2
Firewall:
IP1 - 10.0.0.1
IP2 - 172.16.0.1
Client1 sends it's datagrams to the Firewall:IP1
Client2 sends it's datagrams to the Firewall:IP2
Just before the communication starts I add rules to DNAT udp packets
from Client1 to Client2, and to SNAT packets to Client2 to be from
Firewall:IP2. I do it for the Client2 respective (of course I set up the
ports too).
The problem is that the NAT starts with about 30 seconds delay. tcpdump
shows the packets are coming from Client1 but they are not SNATed &
DNATed. The counters of the rules however counts the packets. Once the
packets begin to be NATed the counters stops.
Can you please tell me where this delay can be coming from?
Thanks in advance:)
reply other threads:[~2005-06-14 9:13 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=42AE9FC1.6050204@borsabg.com \
--to=martin.bangiev@borsabg.com \
--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