tis 2010-05-11 klockan 23:14 +1200 skrev Amos Jeffries: > The v6 worry was that it might have broken v4/v6 gateways. see Bug 2222 > comment #3. This no longer seems to be the case for > non-tcp_outgoing_address configurations. > > mixed v4/v6 usage with tcp_outgoing_address produces a constant "(107) > transport endpoint not connected" for all IPv6-enabled websites (dual as > well as v6-only).
tcp_outgoing set to IPv4 or IPv6? > Bug 2222 re-opened breakage fits the case matrix: > v4->v4 working. > v4->v6 broken. > v6->* broken. Client IP version should not matter. Just tcp_ougoing_address and/or transparent proxy support which implicitly inherits the client IP as tcp_outgoing_address. Regards Henrik
