From: Hannes Eder <heder@google.com>
To: lvs-devel@vger.kernel.org
Cc: "Wensong Zhang" <wensong@linux-vs.org>,
"Julius Volz" <julius.volz@gmail.com>,
lvs-users@linuxvirtualserver.org,
"Laurent Grawet" <laurent.grawet@uclouvain.be>,
"Jean-Luc Fortemaison" <jl.fortemaison@uclouvain.be>,
linux-kernel@vger.kernel.org,
"Jan Engelhardt" <jengelh@medozas.de>,
"Julian Anastasov" <ja@ssi.bg>,
"Simon Horman" <horms@verge.net.au>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
"Fabien Duchêne" <mad_fab@skynet.be>,
"Joseph Mack NA3T" <jmack@wm7d.net>,
"Patrick McHardy" <kaber@trash.net>
Subject: [PATCH v2 0/4] IPVS full NAT support + netfilter 'ipvs' match support
Date: Tue, 29 Sep 2009 14:35:15 +0200 [thread overview]
Message-ID: <20090929123501.13798.84004.stgit@jazzy.zrh.corp.google.com> (raw)
The following series implements full NAT support for IPVS. The
approach is via a minimal change to IPVS (make friends with
nf_conntrack) and adding a netfilter matcher, kernel- and user-space
part, i.e. xt_ipvs and libxt_ipvs.
Example usage:
% ipvsadm -A -t 192.168.100.30:80 -s rr
% ipvsadm -a -t 192.168.100.30:80 -r 192.168.10.20:80 -m
# ...
# Source NAT for VIP 192.168.100.30:80
% iptables -t nat -A POSTROUTING -m ipvs --vaddr 192.168.100.30/32 \
> --vport 80 -j SNAT --to-source 192.168.10.10
or SNAT-ing only a specific real server:
% iptables -t nat -A POSTROUTING --dst 192.168.11.20 \
> -m ipvs --vaddr 192.168.100.30/32 -j SNAT --to-source 192.168.10.10
First of all, thanks for all the feedback. This is the changelog for v2:
- Make ip_vs_ftp work again. Setup nf_conntrack expectations for
related data connections (based on Julian's patch see
http://www.ssi.bg/~ja/nfct/) and let nf_conntrack/nf_nat do the
packet mangling and the TCP sequence adjusting.
This change rises the question how to deal with ip_vs_sync? Does it
work together with conntrackd? Wild idea: what about getting rid of
ip_vs_sync and piggy packing all on nf_conntrack and use conntrackd?
Any comments on this?
- xt_ipvs: add new rule '--vportctl port' to match the VIP port of the
controlling connection, e.g. port 21 for FTP. Can be used to match
a related data connection for FTP:
# SNAT FTP control connection
% iptables -t nat -A POSTROUTING -m ipvs --vaddr 192.168.100.30/32 \
> --vport 21 -j SNAT --to-source 192.168.10.10
# SNAT FTP passive data connection
% iptables -t nat -A POSTROUTING -m ipvs --vaddr 192.168.100.30/32 \
> --vportctl 21 -j SNAT --to-source 192.168.10.10
- xt_ipvs: use 'par->family' instead of 'skb->protocol'
- xt_ipvs: add ipvs_mt_check and restrict to NFPROTO_IPV4 and NFPROTO_IPV6
- Call nf_conntrack_alter_reply(), so helper lookup is performed based
on the changed tuple.
Changes to the linux kernel (rebased to next-20090925):
Hannes Eder (3):
netfilter: xt_ipvs (netfilter matcher for IPVS)
IPVS: make friends with nf_conntrack
IPVS: make FTP work with full NAT support
include/linux/netfilter/xt_ipvs.h | 25 +++++
include/net/ip_vs.h | 2
net/netfilter/Kconfig | 9 ++
net/netfilter/Makefile | 1
net/netfilter/ipvs/Kconfig | 4 -
net/netfilter/ipvs/ip_vs_app.c | 43 ---------
net/netfilter/ipvs/ip_vs_core.c | 37 -------
net/netfilter/ipvs/ip_vs_ftp.c | 178 ++++++++++++++++++++++++++++++++---
net/netfilter/ipvs/ip_vs_proto.c | 1
net/netfilter/ipvs/ip_vs_xmit.c | 30 ++++++
net/netfilter/xt_ipvs.c | 187 +++++++++++++++++++++++++++++++++++++
11 files changed, 418 insertions(+), 99 deletions(-)
create mode 100644 include/linux/netfilter/xt_ipvs.h
create mode 100644 net/netfilter/xt_ipvs.c
Changes to iptables (relative to 1.4.5):
Hannes Eder (1):
libxt_ipvs: user-space lib for netfilter matcher xt_ipvs
configure.ac | 11 +
extensions/libxt_ipvs.c | 365 +++++++++++++++++++++++++++++++++++++
extensions/libxt_ipvs.man | 24 ++
include/linux/netfilter/xt_ipvs.h | 25 +++
4 files changed, 422 insertions(+), 3 deletions(-)
create mode 100644 extensions/libxt_ipvs.c
create mode 100644 extensions/libxt_ipvs.man
create mode 100644 include/linux/netfilter/xt_ipvs.h
next reply other threads:[~2009-09-29 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 12:35 Hannes Eder [this message]
2009-09-29 12:35 ` [PATCH v2 1/4] netfilter: xt_ipvs (netfilter matcher for IPVS) Hannes Eder
2009-09-29 12:35 ` [PATCH v2 2/4] IPVS: make friends with nf_conntrack Hannes Eder
2009-09-29 12:35 ` [PATCH v2 3/4] IPVS: make FTP work with full NAT support Hannes Eder
2009-09-29 12:36 ` [PATCH v2 4/4] libxt_ipvs: user-space lib for netfilter matcher xt_ipvs Hannes Eder
2009-09-29 14:51 ` [PATCH v2 0/4] IPVS full NAT support + netfilter 'ipvs' match support Simon Horman
2009-09-29 15:07 ` Hannes Eder
[not found] ` <b5ddba180909290807j4d1d1d2dl48af9453542612ff@mail.gmail.com>
2009-09-29 23:18 ` Simon Horman
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=20090929123501.13798.84004.stgit@jazzy.zrh.corp.google.com \
--to=heder@google.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=jengelh@medozas.de \
--cc=jl.fortemaison@uclouvain.be \
--cc=jmack@wm7d.net \
--cc=julius.volz@gmail.com \
--cc=kaber@trash.net \
--cc=laurent.grawet@uclouvain.be \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=lvs-users@linuxvirtualserver.org \
--cc=mad_fab@skynet.be \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).