interesting about OSX, NAT64 prefix discovery

Mikael Abrahamsson swmike at
Mon Oct 14 10:57:31 CEST 2013

On Mon, 14 Oct 2013, Simon Perreault wrote:

> Did they implement the NAT64 prefix discovery heuristic? That would be
> great!

Well, I dont know, but this is what happens: THis is without entry in 

dhcp-28-70:~ mikaelabrahamsson$ ping6
PING6(56=40+8+8 bytes) 2001:67c:64:47:b501:73ad:3c6:867c --> 2a00:801::f
16 bytes from 2a00:801::f, icmp_seq=0 hlim=49 time=78.654 ms
16 bytes from 2a00:801::f, icmp_seq=1 hlim=49 time=81.850 ms
--- ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 78.654/80.252/81.850/1.598 ms

dhcp-28-70:~ mikaelabrahamsson$ host has address has IPv6 address 2a00:801::f

Then I put uplift

in /etc/hosts and I get:

hcp-28-70:~ mikaelabrahamsson$ ssh swmike at -v
OpenSSH_5.9p1, OpenSSL 0.9.8y 5 Feb 2013
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug1: Connecting to [] port 22.
debug1: connect to address port 22: No route to host
debug1: Connecting to [2001:db8:624::d4f7:c88f] port 22.
debug1: Connection established.
debug1: identity file /Users/mikaelabrahamsson/.ssh/id_rsa type 1

It's a bit strange, Chrome won't connect either, telnet doesn't work, but 
Safari does work, Firefox connects but it takes a very long time 
(minutes). So perhaps ssh and Safari/Firefox uses a different API call 
than the others?

Mikael Abrahamsson    email: swmike at

More information about the ipv6-ops mailing list