Wednesday, February 22, 2012, 9:47:58 AM, you wrote: > On Feb 22, 2012, at 12:58 AM, Issac Goldstand <mar...@beamartyr.net> wrote:
>> When you say "supports IPv6", we mean IPv6 (ATS) <-- IPv6 (App) or IPv4 >> (ATS) <-- IPv6 (App) or both? (We've established that IPv6 (ATS) <-- >> IPv4 (App) is already supported) Yes, outbound IPv6 has been working for a while, as we've implemented the full functionality in pieces. > I believe the changes at least implies IPv6 <-> IPv6 functionality, but > hopefully also IPv4 <-> IPv6. In proxied (non-transparent) mode you should be able to have any combination. In transparent mode the connections must be the same family for obvious reasons. As for use cases, I think a reasonable one is reverse proxy, IPv4 inbound, IPv6 outbound. I tested that case and it worked. I think that the outbound connection will prefer the same family as the inbound, but it's been a while since I did that. There are still some issues with picking a family when both are available that we will have to work out as we test.
