Op 10-3-2010 18:45, Henrik Nordström schreef: > 3.1.0.17-3 seems to work fine for me on Fedora 12, with IPv4-only > connectivity. (had to drop my IPv6 tunnel for other reasons). But I'll > give it some more in-depth testing of this issue later tonight after > dinner. > > I would suspect the issue is related to the massive amount of IPv6 > addresses Google have, possibly making Squid never getting to the point > that it tries IPv4. > > Jan: Do you have IPv6 connectivity, or only IPv4? Can you also verify > that there is no IPv6 routes present on your server? > Hi Henrik, I don't have any ipv6 connectivity. No ipv6 tunnels whatsoever. However i have never explicitly disabled ipv6 on this server. So i see: [20:12:root@pegasus /etc/sysconfig]# ip route 195.64.90.0/24 dev eth0 proto kernel scope link src 195.64.90.75 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.1 169.254.0.0/16 dev eth0 scope link metric 1002 169.254.0.0/16 dev eth1 scope link metric 1003 default via 195.64.90.1 dev eth0 [20:12:root@pegasus /etc/sysconfig]# ip -f inet6 route unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 [19:18:root@pegasus /etc/sysconfig]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 195.64.90.0 * 255.255.255.0 U 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 eth1 link-local * 255.255.0.0 U 1002 0 0 eth0 link-local * 255.255.0.0 U 1003 0 0 eth1 default lo583.dr3.d12.x 0.0.0.0 UG 0 0 0 eth0 [19:18:root@pegasus /etc/sysconfig]# route -A inet6 Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface fe80::/64 * U 256 0 0 eth0 fe80::/64 * U 256 0 0 eth1 localhost/128 * U 0 7 1 lo fe80::210:18ff:fe32:10a4/128 * U 0 0 1 lo fe80::222:19ff:fe07:5559/128 * U 0 0 1 lo ff00::/8 * U 256 0 0 eth0 ff00::/8 * U 256 0 0 eth1 Should i disable ipv6 on this fedora-fc12 server completely? I have never looked into how to completely disable ipv6 on a fedora box. How do i do that if needed to fix this problem? It looks like squid is first trying ipv6 routes? For which it finds a route? Which of course will never succeed? And never tries ipv4? Can i force squid to ignore the ipv6 routes? If that would be the solution of course... Thanks, -- jan
