netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: juliusv@google.com (Julius Volz)
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
	"Siim Põder" <siim@p6drad-teel.net>,
	"Julian Anastasov" <ja@ssi.bg>,
	"Malcolm Turnbull" <malcolm@loadbalancer.org>,
	"Vince Busam" <vbusam@google.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>
Subject: Re: [rfc 0/3] IPVS: checksum updates
Date: Mon, 8 Sep 2008 13:42:59 +0200	[thread overview]
Message-ID: <20080908114258.GA29477@google.com> (raw)
In-Reply-To: <20080908104120.GB5795@verge.net.au>

On Mon, Sep 08, 2008 at 08:41:22PM +1000, Simon Horman wrote:
> On Mon, Sep 08, 2008 at 12:03:04PM +0200, Julius Volz wrote:
> > On Mon, Sep 8, 2008 at 4:04 AM, Simon Horman wrote:
> > > Hi,
> > >
> > > The impetus for this series of patches is Julian Anastasov noting
> > > that "load balance IPv4 connections from a local process" checks
> > > for 0 TCP checksums. Herbert Xu confirmed that this is not legal,
> > > even on loopback traffic, but that rather partial checksums are
> > > possible.
> > >
> > > The first patch in this series is a proposed solution to handle
> > > partial checksums for both TCP and UDP.
> > >
> > > The other two patches clean things up a bit.
> > >
> > > I have not tested this code beyond compilation yet.
> > 
> > After some first tests, remote connections are still working, but not
> > local ones from the director. The TCP handshake works and the
> > connection is established, but all following packets arriving at the
> > real server have an incorrect TCP checksum.
> > 
> > Btw., this happens both with and without this last series of patches,
> > so I can't get the local client feature working at all. Looking at it
> > further...
> 
> Ok, is this for both IPv4 & IPv6? Does it still occur with just the first
> patch in this series applied?

It's for both, although I only tested IPv4 at first. Here is a complete
test matrix of what works when:

CR = connection refused
T = connection timeout
C = connection established, but not working afterwards
OK = working

			remote client |	local client
COMMIT			v4	v6    |	v4	v6
======================================|=================
CSUM 3/3		OK	T     |	C	T
CSUM 2/3		OK	T     |	C	T
CSUM 1/3		OK	T     |	OK	T
W/O CSUM		OK	T     |	C	T
...				      |
f2428ed5		OK	T     |	CR	CR
4856c84c		OK	CR    |	CR	CR
f94fd041 (my last one)	OK	OK    |	CR	CR

So the last time that IPv6 was working _at all_ was at my last commit of
the big v6 series...

Julius

-- 
Julius Volz - Corporate Operations - SysOps

Google Switzerland GmbH - Identification No.: CH-020.4.028.116-1

  reply	other threads:[~2008-09-08 11:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  2:04 [rfc 0/3] IPVS: checksum updates Simon Horman
2008-09-08  2:04 ` [rfc 1/3] ipvs: handle PARTIAL_CHECKSUM Simon Horman
2008-09-08  7:24   ` Herbert Xu
2008-09-08  9:05     ` Simon Horman
2008-09-08  9:54       ` Herbert Xu
2008-09-08  2:04 ` [rfc 2/3] ipvs: Use inet_proto_csum_replace*() Simon Horman
2008-09-08  2:04 ` [rfc 3/3] ipvs: Consolidate checksuming code Simon Horman
2008-09-08 10:03 ` [rfc 0/3] IPVS: checksum updates Julius Volz
2008-09-08 10:41   ` Simon Horman
2008-09-08 11:42     ` Julius Volz [this message]
2008-09-08 11:57       ` Simon Horman
2008-09-08 12:04         ` Simon Horman
2008-09-08 12:14           ` Julius Volz
2008-09-08 12:34             ` Simon Horman
2008-09-08 13:12               ` Julius Volz
2008-09-08 13:20                 ` Simon Horman
2008-09-08 13:42                   ` Julius Volz
2008-09-08 15:32                     ` Julius Volz
2008-09-08 23:22                       ` Simon Horman
2008-09-08 23:40 ` Simon Horman
2008-09-09  9:30   ` Julius Volz
2008-09-09 11:31     ` Simon Horman
2008-09-10 17:30       ` Julius Volz
2008-09-10 23:29         ` Simon Horman
2008-09-11 13:07           ` Wensong Zhang
2008-09-11 13:45             ` Simon Horman
2008-09-11 13:55               ` Julius Volz
2008-09-11 14:43                 ` Wensong Zhang

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=20080908114258.GA29477@google.com \
    --to=juliusv@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=lvs-devel@vger.kernel.org \
    --cc=malcolm@loadbalancer.org \
    --cc=netdev@vger.kernel.org \
    --cc=siim@p6drad-teel.net \
    --cc=vbusam@google.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 NNTP newsgroup(s).