Hi All,
I have running an IPv6 Tunnel Broker. When I configure a Windows 8 client with a (static) IPv6 and do a traceroute,
it nicely goes to the destination (google.com).
When I setup (different IPv6 address offcourse) on a CentOS 6.3 machine and do a traceroute, it stops at the UTM 9!
If I ping from the CentOS machine (ping6) to google.com, I receive a reply. How is this possible?
When I go in UTM 9 to Support>Tools>Traceroute and do a traceroute (IPv4 or IPv6, doesn't matter) I see that it's also not woking:
traceroute to google.com (2a00:1450:400c:c03::8b), 30 hops max, 40 byte packets using UDP
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
Why is it working good from a Windows 8 machine and not from a Centos machine or the UTM itself????
What am I missing?
I have running an IPv6 Tunnel Broker. When I configure a Windows 8 client with a (static) IPv6 and do a traceroute,
it nicely goes to the destination (google.com).
When I setup (different IPv6 address offcourse) on a CentOS 6.3 machine and do a traceroute, it stops at the UTM 9!
If I ping from the CentOS machine (ping6) to google.com, I receive a reply. How is this possible?
When I go in UTM 9 to Support>Tools>Traceroute and do a traceroute (IPv4 or IPv6, doesn't matter) I see that it's also not woking:
traceroute to google.com (2a00:1450:400c:c03::8b), 30 hops max, 40 byte packets using UDP
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
Why is it working good from a Windows 8 machine and not from a Centos machine or the UTM itself????
What am I missing?