Moser, Stefan (SIDB) wrote:
Amos, Henrik,
http_access allow to_ipv6 !to_ipv6 did work, squid now seems to work as
required and can access both single (IPv4 or IPv6) and dual-stack (IPv4 and IPv6)
destinations.
I´m going to play with the configuration within the next days and post a
summary
Amos, Henrik,
http_access allow to_ipv6 !to_ipv6 did work, squid now seems to work as
required and can access both single (IPv4 or IPv6) and dual-stack (IPv4 and
IPv6) destinations.
I´m going to play with the configuration within the next days and post a
summary of my findings, this may be
Hi,
we are testing with squid, latest beta, in a dual-stack configuration:
squid is running on SLES 11. Server has 1 interface card only, configured with
an IPv4 and IPv6 address, both running on standard 3128 port. Server has true,
native IPv4 and IPv6 internet connectivity (no IPv6 tunnel
Moser, Stefan (SIDB) wrote:
Hi,
we are testing with squid, latest beta, in a dual-stack
configuration:
squid is running on SLES 11. Server has 1 interface card only,
configured with an IPv4 and IPv6 address, both running on standard
3128 port. Server has true, native IPv4 and IPv6 internet
fre 2009-10-30 klockan 13:33 +1300 skrev Amos Jeffries:
Yes. The magic is not complete and has a point of failure.
Another idea. Why don't we address this in another way, making
tcp_outgoing_address select an IPv4+IPv6 pair of addresses?
I don't see how it can be made to work properly for
Henrik Nordstrom wrote:
fre 2009-10-30 klockan 13:33 +1300 skrev Amos Jeffries:
Yes. The magic is not complete and has a point of failure.
Another idea. Why don't we address this in another way, making
tcp_outgoing_address select an IPv4+IPv6 pair of addresses?
I don't see how it can be
fre 2009-10-30 klockan 14:01 +1300 skrev Amos Jeffries:
I'm looking at a few approaches;
having Squid kick off the DNS test earlier on in the processing. So
that the data may be available later as needed, but not hold up the
processing.
I think the right there is to move tcp_outgoing_*
