• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

HE Tunnel on Mac OS X - unpredictable results

Started by tiquetonne44, May 17, 2014, 06:19:09 AM

Previous topic - Next topic

tiquetonne44

Hi all,

I have a pretty standard setup.  A GIF tunnel that provides me with IPv6 connectivity that is established directly on an Imac.  From my mac I can access all IPv6 sites and my en0 and en1 interfaces and Airport (bridge mode) received automatic addressing from the /64 block that I HE has allocated me (rtadvd is running on my en0 interface).

For reasons that are beyond the scope of the following post, I have elected to establish the HE tunnel directly on my Mac and not on the  Airport.  The problem that I'm experiencing concerns wifi devices that connect to my Airport. For example, my ipad receives IPv4/IPv6 address allocation from the /64, however, I am unable to ping remote IPv6 servers from my device consistently and after about the 5th or 6th ping I receive a no "route to host message."  Example:

ping6 -I en1 cisco.com
PING6(56=40+8+8 bytes) 2001:470:1f12:xxxx:ac32:e78f:c601:2393 --> 2001:420:1101:1::a
16 bytes from 2001:420:1101:1::a, icmp_seq=0 hlim=244 time=135.803 ms
16 bytes from 2001:420:1101:1::a, icmp_seq=1 hlim=244 time=125.905 ms
16 bytes from 2001:420:1101:1::a, icmp_seq=2 hlim=244 time=125.719 ms
16 bytes from 2001:420:1101:1::a, icmp_seq=3 hlim=244 time=125.602 ms
16 bytes from 2001:420:1101:1::a, icmp_seq=4 hlim=244 time=137.463 ms
16 bytes from 2001:420:1101:1::a, icmp_seq=5 hlim=244 time=126.297 ms
ping6: sendmsg: No route to host
ping6: wrote cisco.com 16 chars, ret=-1

Please note that when I work on my mac I never experience this problem.

Finally, my en0 interface has a fixed IP address (with the HE tunnel's :2 address as its gateway) and if I try to ping the same destination, I receive consistently the "no route to host" message.  That said, this IPv6 address is the default gateway for a number of VM that I run on my mac and they are all able to access the IPv6 internet, so I'm not really sure what this doesn't work, though what I'm sure about is that there's a connection between the above and this problem.

[ten-eth0:~] Oothoon% ping6 -I en0 cisco.com
PING6(56=40+8+8 bytes) 2001:470:1f12:xxxx::3 --> 2001:420:1101:1::a
ping6: sendmsg: No route to host
ping6: wrote cisco.com 16 chars, ret=-1
ping6: sendmsg: No route to host

The default route of my Mac is the :1 of the tunnel endpoint.  Any ideas what the problem is?

Kind regards,

Andrew