netdev - Re: [rfc 0/3] IPVS: checksum updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f4845fc0809080642t1629ed27ld9087d788828d24d@mail.gmail.com>
Date:	Mon, 8 Sep 2008 15:42:17 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Simon Horman" <horms@...ge.net.au>
Cc:	lvs-devel@...r.kernel.org, netdev@...r.kernel.org,
	"Siim Põder" <siim@...rad-teel.net>,
	"Julian Anastasov" <ja@....bg>,
	"Malcolm Turnbull" <malcolm@...dbalancer.org>,
	"Vince Busam" <vbusam@...gle.com>,
	"Herbert Xu" <herbert@...dor.apana.org.au>
Subject: Re: [rfc 0/3] IPVS: checksum updates

On Mon, Sep 8, 2008 at 3:20 PM, Simon Horman <horms@...ge.net.au> wrote:
> On Mon, Sep 08, 2008 at 03:12:39PM +0200, Julius Volz wrote:
>> On Mon, Sep 8, 2008 at 2:34 PM, Simon Horman <horms@...ge.net.au> wrote:
>> > On Mon, Sep 08, 2008 at 02:14:12PM +0200, Julius Volz wrote:
>> >> I'm actually looking at that case now (4856c84c1358b, but with the fix
>> >> above). It seems that the NAT isn't working (DR works, by the way!).
>> >> At least the first packet arriving at the real server still has the
>> >> client's IP as the source (in the v6 case)...
>> >
>> > Ok, I'm looking at NAT with 4856c84c1358b + that fix too too,
>> > but on v4 :-)
>> >
>> >> Let's wait with reverting the local client patches until tomorrow...
>> >> maybe I can find the problem until then.
>> >
>> > Ok, I was just concerned that this might hold up merging
>> > your code into Dave's tree for too long, thats all.
>>
>> Ok, with my last patch (and your two/three last ones reverted), I get
>> everything working except IPv6 with a local client...
>
> Ok, that is good news :-)
>
> Sorry for the stuff up. That bugus ip_route_me_harder() call
> was caused by me trying to merge the IPv6 patches with the local
> client patches.

No problem!

> 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...

> I'll drop CSUM2/3 and 3/3 for now, they aren't essential and
> it really ought to be a matter of (me) sitting down and fixing
> some correctness issues.

Ok!

> Its the end of my day now. I'll try and update lvs-next-2.6 into
> a working state in the morning.

Yes, let's stabilize it a bit... have a nice evening!

Julius

-- 
Julius Volz - Corporate Operations - SysOps

Google Switzerland GmbH - Identification No.: CH-020.4.028.116-1
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html