Henrik Nordström wrote:
This is one of those odd bug reports which users encounter in the field
when running a packaged Squid (Fedora).
If Squid is build with IPv6 support enabled (which Fedora 12 Squid is),
but the host for some reason do not have IPv6 support enabled then the
binary will fail with "comm_open: socket failure: (97) Address family
not supported by protocol"
Question is, do we consider this a bug or just a misconfigured host?
https://bugzilla.redhat.com/show_bug.cgi?id=548903
Note that Fedora 12 by default do have IPv6 support enabled in even if
unconfigured. Special host configuration is needed to completely disable
IPv6 support triggering this issue (see Fedora bug report above).
But I can imagine other distributions may give the user an easy option
to fully disable IPv6 support if they want.
Users compiling their own kernels may also run into this issue.
Regards
Henrik
This is another side of the missing split-stack support.
The particular DNS issues he mentions are, I believe, resolved by the
split-stack support currently in 3.HEAD. However, there are issues
further down in forwarding still to be resolved before I'm happy
back-porting it.
What was that old 3.0 saying? "Real soon now".
Meanwhile there is a perfectly working solution with --disable-ipv6 and
rebuild Squid.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21
Current Beta Squid 3.1.0.15
