On Tue, Jun 21, 2016 at 12:26:17PM +0200, Jiri Tulach wrote: > Hello, > Ok, just think about it. > > The intention of SIIT-DC is to provide a way how to operate IPv6 only data > center. You have to translate IPv4 request to IPv6 and do it so that client > source address is preserved. It is done by adding IPv6 prefix to IPv4 > address. > > All you need is to have IPv4 frontend connected to IPv6 backend where client > source IPv4 address is translated to IPv6. Maybe some option in HaProxy > "source" configuration directive could do the same trick. > > In this case two frontends (IPv6 and IPv4) will be connected to one backend > (IPv6 with IPv4to6 client source address mapping).
I think you didn't understand what I meant. HAProxy *is* a proxy and by this it by default "translates" addresses. A lot of people are using it to provide IPv6 connectivity to an IPv4-only service for example. What SIIT-DC is about is just a stateless translation in the sense that it doesn't require the knowledge of a TCP session nor anything, it operates on packets. It's made on purpose for products like routers which do *not* have the ability to deal with a connection. Here not only we have connections but we can decide how to map addresses and it's stateful. That's why it's totally out of scope and irrelevant. Regards, Willy
