Hudson build is back to normal: 3.1-amd64-CentOS-5.3 #141

See

Re: trunk ipv6 split-stack configure test issues

Henrik Nordström wrote: fre 2010-05-14 klockan 07:09 +0200 skrev Henrik Nordström: The configure test for ipv6 split-stack configuration fails if there is IPv6 headers but the build host do not have IPv6 enabled. Correction, it's the v4mapped test that fails. Please try to figure out a compi

Build failed in Hudson: 3.HEAD-amd64-CentOS-5.3 #531

See Changes: [Henrik Nordstrom ] Clean up use of commResetFD when socket incompatible with requested address This patch backs out part of the patch for Bug # and replaces it by crudely cycling over the available addresse

Re: [MERGE] [3.1] Fall back on IPv4 if IPv6 is not present

fre 2010-05-14 klockan 16:47 +1200 skrev Robert Collins: > +1 Applied.

Build failed in Hudson: 3.1-amd64-CentOS-5.3 #140

See Changes: [Henrik Nordstrom ] Clean up use of commResetFD when socket incompatible with requested address This patch backs out part of the patch for Bug # and replaces it by crudely cycling over the available addresses,

Re: trunk ipv6 split-stack configure test issues

fre 2010-05-14 klockan 07:09 +0200 skrev Henrik Nordström: > The configure test for ipv6 split-stack configuration fails if there is > IPv6 headers but the build host do not have IPv6 enabled. Correction, it's the v4mapped test that fails. > > Please try to figure out a compile-only test if poss

trunk ipv6 split-stack configure test issues

The configure test for ipv6 split-stack configuration fails if there is IPv6 headers but the build host do not have IPv6 enabled. Please try to figure out a compile-only test if possible. Regards Henrik

Re: [MERGE] [3.1] Fall back on IPv4 if IPv6 is not present

+1

[MERGE] [3.1] Fall back on IPv4 if IPv6 is not present

The attached patch makes squid automatically fall back on IPv4 operation if it fails creating an IPv6 socket. This may happen if Squid is built with IPv6 support enabled but no IPv6 stack is available when it runs. # Bazaar merge directive format 2 (Bazaar 0.90) # revision_id: hen...@henriknordstro

Re: [MERGE] [3.1] Clean up commReset use in combination with tproxy or tcp_outgoing_address

fre 2010-05-14 klockan 03:46 +0200 skrev Henrik Nordström: > Take three merged.

Build failed in Hudson: 3.1-i386-opensolaris #76

See Changes: [Henrik Nordstrom ] Correct F->sock_family setting on accept sockets, ipv6/ipv4 compile condition was reversed [Amos Jeffries ] Author: Wojciech Zatorski Bug 2919: tcp_outgoing_address ACLs not obeying acl_uses_in

[MERGE] [3.1] Clean up commReset use in combination with tproxy or tcp_outgoing_address

Take three Differences from take two is that * the test for IPv6 over IPv4 have been corrected, was triggering a bit too much, blocking IPv6 access if tcp_outgoing_address not set * Set errno to ENETUNREACH when destination blocked by family, to match what Linu

Re: [MERGE] [3.1] Clean up commReset use in combination with tproxy or tcp_outgoing_address

fre 2010-05-14 klockan 11:23 +1200 skrev Amos Jeffries: > It does not mark IPv6 'BAD' in the case where the link is down or boudn > wrong. This is fine since the failover works, but we may want to look > into it later. Not 100% sure what you try to say here The following is intentional however

Re: [MERGE] [3.1] Clean up commReset use in combination with tproxy or tcp_outgoing_address

Henrik Nordström wrote: Take two. The change is that this version also tries to skip IPv4 addresses if the socket is IPv6-only. This case should have been handled by existing code paths, but the way that was done was quite twisted and apparently broke down by my changes to commResetFD. This pa

[MERGE] [3.1] Clean up commReset use in combination with tproxy or tcp_outgoing_address

Take two. The change is that this version also tries to skip IPv4 addresses if the socket is IPv6-only. This case should have been handled by existing code paths, but the way that was done was quite twisted and apparently broke down by my changes to commResetFD. This patch backs out part of the