netdev - Re: Adding SNAT support to LVS/NAT

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: <f4845fc0809140339p1d3be327j98ddcb02c4efc786@mail.gmail.com>
Date:	Sun, 14 Sep 2008 12:39:29 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Joseph Mack NA3T" <jmack@...d.net>
Cc:	lvs-devel@...r.kernel.org, netdev@...r.kernel.org,
	j.stubbs@...kthink.co.jp
Subject: Re: Adding SNAT support to LVS/NAT

On Sun, Sep 14, 2008 at 3:37 AM, Joseph Mack NA3T <jmack@...d.net> wrote:
> On Sun, 14 Sep 2008, Julius Volz wrote:
>
>> So maybe it would already work? ;)
>
> No. Some highly motivated people tried doing SNAT on OUTPUT in an attempt to
> do F5-SNAT and it didn't work. This lead to the write up in
>
> http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.non-modified_realservers.html#F5_snat
>
> which brings us to where we are now.

Thanks for the info! Right, I even said myself in the previous reply
that ip_vs_postrouting() stops further processing in the POSTROUTING
chain, so it never reaches netfilter NAT code.

I still think an in-IPVS SNAT would be nice anyways... don't know if
I'll find the time to hack on it soon, though.

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