@johnpoz Do you have any other ideas, I have it set to listen on ipv6 and ipv4 I can see it bind to my interface on both addresses but if a machine connects to the proxy with an ipv6 source address the proxy gives a 409 error. Everything else works, this is in HE tunnel broker configuration, I see states that get established, again ipv6 does not do nat but I would assume that if it has the option to listen on ipv6 addresses that it would proxy the addresses, if I put the machine on the guest network without the proxy the system functions, so I know my IPV6 only settings on the side of HE tunnel work. What am I missing, I also configured tcp outgoing testing with the ipv6 for ipv6 and that was the same thing, so I turned it back to outgoing auto. I know it supports it per the Squid website, I also tried to do a http_port :: 3128 test same thing. I just wonder what is causing squid to not proxy ipv6 traffic I have tested in all transparent and non-transparent with ssl intercept.
Any ideas? Thanks again for working with me on getting me comfortable with ipv6, I just feel there is something I am missing for the proxy.
I have not tested this
#acl localnet src fc00::/7 # RFC 4193 local private network range
#acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
Have you ever had it configured where ipv6 source addresses work? I have it working when it is ipv4 going to say ipv6.google.com the proxy sees the address source is my local machine ipv4 destination ipv6 and it connects, my ipv6 tests work, but if anything is a source of ipv6 it fails.