From: Julian Anastasov <ja@ssi.bg>
To: "longguang.yue" <bigclouds@163.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Simon Horman <horms@verge.net.au>,
lvs-devel@vger.kernel.org, yuelongguang@gmail.com
Subject: Re: a question about fullnat mode for ipvs
Date: Mon, 26 Oct 2020 22:23:42 +0200 (EET) [thread overview]
Message-ID: <615db10-72af-2a86-dde2-61af8e6bd80@ssi.bg> (raw)
In-Reply-To: <1989ac03.3737.175445ba5f9.Coremail.bigclouds@163.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Hello,
On Tue, 20 Oct 2020, longguang.yue wrote:
> Hi,all:
> fullnat mode refers to incoming packet's src:port and dst:port pairs are both changed at the same
> time, vice versa for outgoing packets.
> fullnat has existed for many years since 2009, why which is not in kernel.
Not sure. What I see now is that it adds some complexity
to the code. Open questions are about integration with netfilter
conntracks (when conntrack=1), in the sync protocol, etc.
> introduction for fullnat http://kb.linuxvirtualserver.org/wiki/IPVS_FULLNAT_and_SYNPROXY
>
> could we port or re-implement it in upstream?
May be I don't fully understand the goals but
is it worth it?
Regards
--
Julian Anastasov <ja@ssi.bg>
prev parent reply other threads:[~2020-10-26 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 20:13 [PATCH v8 net-next] ipvs: inspect reply packets from DR/TUN real servers Julian Anastasov
2020-10-12 0:02 ` Pablo Neira Ayuso
[not found] ` <1989ac03.3737.175445ba5f9.Coremail.bigclouds@163.com>
2020-10-26 20:23 ` Julian Anastasov [this message]
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=615db10-72af-2a86-dde2-61af8e6bd80@ssi.bg \
--to=ja@ssi.bg \
--cc=bigclouds@163.com \
--cc=horms@verge.net.au \
--cc=lvs-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=yuelongguang@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).