netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Julius Volz <juliusv@google.com>
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: Tue, 9 Sep 2008 09:22:06 +1000	[thread overview]
Message-ID: <20080908232203.GD13048@verge.net.au> (raw)
In-Reply-To: <f4845fc0809080832w69f8aab2q12b63e0a8f6f1fdf@mail.gmail.com>

On Mon, Sep 08, 2008 at 05:32:47PM +0200, Julius Volz wrote:
> On Mon, Sep 8, 2008 at 3:42 PM, Julius Volz <juliusv@google.com> wrote:
> > On Mon, Sep 8, 2008 at 3:20 PM, Simon Horman <horms@verge.net.au> wrote:
> >> I'm not so concerned about IPv6 local not working for now -
> >> its a combination of two new features. And hopefully we
> >> can iron it out in the not to distant future anyway.
> >
> > Yes, probably just some minor bug...
> 
> Actually, it wasn't even a kernel bug, but a configuration error - I
> was using LVS/NAT, but still had the dummy0 interface with the IPv6
> VIP configured on the real server (from the DR case). And in the local
> client case, the source address is the VIP, so the real server just
> delivered the response to itself.
> 
> Now I can confirm that everything is working (without your last two
> patches and with the one removing the wrong ip_route_me_harder)!

Great!

  reply	other threads:[~2008-09-08 23:22 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
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 [this message]
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=20080908232203.GD13048@verge.net.au \
    --to=horms@verge.net.au \
    --cc=herbert@gondor.apana.org.au \
    --cc=ja@ssi.bg \
    --cc=juliusv@google.com \
    --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).