From: "Тен Лев" <leo.ten@gmail.com>
To: netfilter@vger.kernel.org
Subject: conntrackd and natted tcp sessions
Date: Tue, 18 Aug 2015 19:38:12 +0600 [thread overview]
Message-ID: <55D33544.7050200@gmail.com> (raw)
Hello!
I have a problem running conntrackd in active-active mode. My setup is:
2 nat boxes in 2 different data centers - natbox1 and natbox2
From each DC a single network is broadcasted through BGP, so both
natboxes have the same IP.
Behind nat boxes are networks with addresses 10.0.0.0/16 and
10.0.1.0/16, and there is a l2 tunnel between them, so all hosts in
these networks are accessible to each other.
There are identical servers in both DCs in 10.0/16 networks -server1 and
server2. Let's say the address of one of them is 10.0.1.2 and the second
has address 10.0.0.2.
server1 is behind natbox1 and server2 is behind natbox2.
The problem I am trying to solve is that when server1 sends a TCP
request (HTTP for example) and the remote server is replying to the
natbox2 in another DC, instead of natbox1 due to the fact, that it is
'closer' to it, the reply should be delivered from natbox2 to server1,
that initially sent the request through the tunnel between natboxes.
Conntrackd perfectly syncs states and writes them into the kernel
conntrack tables of natboxes, request gets to the natbox2, but never
leaves it to server1.
Everything is working for UDP and ICMP packets. But TCP gets stuck on
the natbox and never gets sent to the correct server. And also if
requests and relies go through the same DC TCP connections also work.
I am running Ubuntu 14.04.3 LTS on Linux natbox2.reg.ru
3.13.0-61-generic. All server are KVM virtual machines.
Thanx in advance!
leo
leo.ten@gmail.com
next reply other threads:[~2015-08-18 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 13:38 Тен Лев [this message]
2015-08-18 17:34 ` conntrackd and natted tcp sessions Pablo Neira Ayuso
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=55D33544.7050200@gmail.com \
--to=leo.ten@gmail.com \
--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 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.