From: Patrick McHardy <kaber@trash.net>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, netfilter@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Malcolm Turnbull <malcolm@loadbalancer.org>,
Mark Brooks <mark@loadbalancer.org>,
Wensong Zhang <wensong@linux-vs.org>,
Julius Volz <julius.volz@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Hannes Eder <heder@google.com>,
Jan Engelhardt <jengelh@medozas.de>
Subject: Re: [patch v2.8 2/4] IPVS: make friends with nf_conntrack
Date: Fri, 23 Jul 2010 12:47:28 +0200 [thread overview]
Message-ID: <4C497340.1010305@trash.net> (raw)
In-Reply-To: <20100722075012.658190199@vergenet.net>
Am 22.07.2010 09:35, schrieb Simon Horman:
> Update the nf_conntrack tuple in reply direction, as we will see
> traffic from the real server (RIP) to the client (CIP). Once this is
> done we can use netfilters SNAT in POSTROUTING, especially with
> xt_ipvs, to do source NAT, e.g.:
>
> % iptables -t nat -A POSTROUTING -m ipvs --vaddr 192.168.100.30/32 --vport 80 \
>> > -j SNAT --to-source 192.168.10.10
Applied, thanks.
next prev parent reply other threads:[~2010-07-23 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 7:35 [patch v2.8 0/4] IPVS full NAT support + netfilter 'ipvs' match support Simon Horman
2010-07-22 7:35 ` [patch v2.8 1/4] netfilter: xt_ipvs (netfilter matcher for IPVS) Simon Horman
2010-07-23 10:44 ` Patrick McHardy
2010-07-22 7:35 ` [patch v2.8 2/4] IPVS: make friends with nf_conntrack Simon Horman
2010-07-23 10:47 ` Patrick McHardy [this message]
2010-07-22 7:35 ` [patch v2.8 3/4] IPVS: make FTP work with full NAT support Simon Horman
2010-07-23 10:49 ` Patrick McHardy
2010-07-22 7:35 ` [patch v2.8 4/4] [patch v2.2 4/4] [PATCH v2.1 4/4] libxt_ipvs: user-space lib for netfilter matcher xt_ipvs Simon Horman
2010-07-23 10:52 ` Patrick McHardy
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=4C497340.1010305@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=heder@google.com \
--cc=horms@verge.net.au \
--cc=jengelh@medozas.de \
--cc=julius.volz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=malcolm@loadbalancer.org \
--cc=mark@loadbalancer.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=wensong@linux-vs.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;
as well as URLs for NNTP newsgroup(s).