I just switched over to 9.080 from 9.005. As before, I am using a 6in4 tunnel from Hurricane Electric. I am using the same tunnel as I was with 9.005. Now that I switch over to 9.080, utm is allocating ipv6 addresses and they are visible within the network, but when I view the address externally, the address that shows up is the client side of the tunnel, not the address of the host. I looked at the settings and they are all the same. Has anyone else experienced this? I don't think this is correct, because the client side of the tunnel is not intended to be used other than for the tunnel. The addresses allocated to the hosts aren't even in the same /64 subnet as the client end of the tunnel.
I agree with you. Without Masquerading/NAT or a proxy you should see the client ip address on whatismyipv6 or a similar website. Unfortunately I wasn't able to reproduce it till now. [:(]
Is the HTTP proxy enabled on your UTM and do you get any iptables rules with "ip6tables -t nat -vnL USR_POST"?
I used freenet6 as tunnel broker and the ip addresses from the allocated subnet for the internal network.
cheers, Daniel
Windows has detected you do not have a keyboard. Press 'F9" to continue.
I agree with you. Without Masquerading/NAT or a proxy you should see the client ip address on whatismyipv6 or a similar website.
Unfortunately I wasn't able to reproduce it till now. [:(]
Is the HTTP proxy enabled on your UTM and do you get any iptables rules with "ip6tables -t nat -vnL USR_POST"?
I used freenet6 as tunnel broker and the ip addresses from the allocated subnet for the internal network.
cheers,
Daniel
Thanks for the reply. I'm overseas for two weeks so I can't look at anything from here. However, I have not enabled any http proxies. The beta software is configured exactly the same way as it was on the release software.
I just did a clean reinstallation of 9.100-8 (i.e., from scratch in a new VM) and this problem is no longer present. The ipv6 address of the host is showing up when I run ipv6 tests, NOT the ipv6 address of the client side of the tunnel.
I'm not aware of anything that I configured differently this time from last time. However, before I cut over to this installation, I was using my old 9.0 installation and it was working properly as well, so the problem may be related to something in the earlier beta or the configuration of the earlier beta.
I just did a clean reinstallation of 9.100-8 (i.e., from scratch in a new VM) and this problem is no longer present. The ipv6 address of the host is showing up when I run ipv6 tests, NOT the ipv6 address of the client side of the tunnel.
I'm not aware of anything that I configured differently this time from last time. However, before I cut over to this installation, I was using my old 9.0 installation and it was working properly as well, so the problem may be related to something in the earlier beta or the configuration of the earlier beta.
