I don't know when the http proxy started rejecting ipv6 requests but I first noticed it in 7.890 and its still broke in 7.891. Only way to surf using a tunnel broker is to have a allow--http--anyIPv6 rule for IPv6 traffic in packet filter rules.
Sounds strange, and we currently don't observe this problem here. Does IPv6 work for you in general? Does ping ipv6.google.com work? Have you seen any related messages in the logfiles? The output of 'netstat -tunlp' would be helpful too.
My setup:
1. Http transparent proxy only.
2. No packet filter rules for http traffic (ipv4). Can browse the internet no problem ipv4.
3. Tunnel connected to freenet six (ipv6). Can't connect to the internet. nslookup etc give ipv6 results, ping works fine.(screenshot).
4. Everthing ok if i create a packet filter rule allow -->internal network-->anyIPv6 (which bypasses proxy but it shouldn't go to the packet filter since the proxy should intercept it.)
5. Default drop in packet filter log (screenshot3.) without any packet filter rules.
My setup:
1. Http transparent proxy only.
2. No packet filter rules for http traffic (ipv4). Can browse the internet no problem ipv4.
3. Tunnel connected to freenet six (ipv6). Can't connect to the internet. nslookup etc give ipv6 results, ping works fine.(screenshot).
4. Everthing ok if i create a packet filter rule allow -->internal network-->anyIPv6 (which bypasses proxy but it shouldn't go to the packet filter since the proxy should intercept it.)
5. Default drop in packet filter log (screenshot3.) without any packet filter rules.
