The Base system still has IPv6 support; however some of the Bind DNS servers I am using do not, which causes a server failure when attempting to do an IPV6 AAAA name resolution request. This was causing some problems with configuring a parent server by DNS name on some other systems that are now in production. Disabling IPv6 in squid fixed those problems, I figured the 3.1.6 would be out before I was ready to put this system in production use and thought doing its configuration and testing with the 3.1.5.1 wouldn't hurt until then. Guess I could have waited one more day to start testing and I wouldn't have run into this problem, 3.1.6 is compiling on this system now. Thanks, Dean Weimer Network Administrator Orscheln Management Co > -----Original Message----- > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Monday, August 02, 2010 6:51 PM > To: squid-users@xxxxxxxxxxxxxxx > Subject: Re: Squid 3.1.5.1 --disable-ipv6 possibly not working? > > On Mon, 2 Aug 2010 15:25:49 -0500, "Dean Weimer" <dweimer@xxxxxxxxxxxx> > wrote: > > I just built a new proxy server running FreeBSD 7.3 and Squid 3.1.5.1 > > compile with the following options. > > > <snip> > > Yes the 3.1.5.1 package has some IPv6 bugs in IPv4-only systems. Thus the > .1 (beta status). > These have been resolved to the best of my knowledge in the followup 3.1.6 > package which is available now. > > If you were using --disable-ipv6 for reasons of custom kernel builds with > stack customization or IPv6 being disabled in the system and failovers not > working, those problems have also fixed in the 3.1.6 package. > > Amos
