Tag Info

Hot answers tagged

7

This has changed a little with 10.7. It's no longer done via @computername.mobilemename.members.mac.com, it's now done via members.btmm.icloud.com, and its no longer as simple as your mobilemename. Step 1: Find out your iCloud BTMM domain Either of these commands will provide your BTMM domain: # dns-sd -E # mDNS -E The output is formatted slightly ...


6

I assume you're talking about on your Mac since you don't specify. Yes you can do this but in all likelihood, you won't see much other than your internet connection probably won't work. Most ISPs (Internet Service Providers) are not yet ready to handle IPv6 traffic and many won't be right up to IPv6 day on June 8th 2011. Many won't be ready beyond then ...


5

Currently OS X does not have a DHCPv6 client built in. Note that in OS X the IPv4 configuration gives you a choice of manual, DHCP, DHCP with manual DNS, BOOTP, or off. The IPv6 choices are manual, automatic, link-local, and off. The "Automatic" is not DHCP, it's autoconfig from a router. With IPv6, there are multiple ways to get an address. OS X doesn't ...


4

Actually yes it does have a DHCPv6 client. I have verified in 10.8.4 but the email thread referenced above talks about it working with Lion too. To get it to work, you need to set the IPv6 configuration to "automatic" and then on your router, you also need to configure the routing announcements to indicate that hosts should use DHCP to obtain an address. I ...


3

You probably already read did-you-realize-apples-back-to-my-mac-mobileme-service-uses-ipv6 by now. It has some of the answers. Also https://en.wikipedia.org/wiki/KAME_project I don't know how much was changed since MobileMe became iCloud. lsof -i:4500 Shows that the process 'racoon' is handling the tunnel. This port is also opened on the router. I wonder ...


3

I read a few articles on the underpinning of Back To My Mac and supposedly some people have effectively connected via ssh, check out the discussion contained in this Macworld post. The best post in the thread is as follows: Use the following format for connecting as a differnent username: ssh user.name@hostname.username.members.mac.com. If ...


3

Short answer: mir:~ itorres$ ndp -an Neighbor Linklayer Address Netif Expire St Flgs Prbs ::1 (incomplete) lo0 permanent R 2001:470:95e5:1:3583:ead0:514d:d459 e8:6:88:ca:fd:7c en0 permanent R 2001:470:95e5:1:ea06:88ff:feca:fd7c e8:6:88:ca:fd:7c en0 permanent R ... Longer ...


2

That's because the IP addresses for resolution are version 6. If you use ping6 or traceroute6 you can reach your host as well.


2

Big thanks to hobs and ghoppe who both had workable solutions. The main problem is that MobileMe Back To My Mac uses IPv6 addressing if available and perhaps exclusively, so I didn't think to use ping6 or traceroute6 and ssh is apparently smart enough to resolve either IPv4 or IPv6. ssh -p 22 username@computername.mobilemename.members.mac.com. works very ...


2

You can ssh to your machine which has "Bac to my Mac" enabled like this: ssh -p 22 username@computername.mobilemename.members.mac.com


2

A possibility The lack of progress, beyond the firewall-related message, may be unrelated to the firewall or networking. For example, these two lines from Intel Mac Pro Stuck on Gray Apple screen before OS load (2010-07-17): IPv6 packet filtering initialized, default to accept, logging disabled Jul 15 22:08:39 kextd[25]: kextd_watch_volumes: Couldn't set ...


1

Right, slightly late, but I had the same problem. Although my circumstances vary a little. I am using a FortiGate FW instead. The solution should be almost the same though. You can read my "guides" on this here: http://blog.belodedenko.me/2013/07/dynamic-ipv6-updates-using-ddclient-for.html ...


1

Issue resolved by turning off GlimmerBlocker.


1

Make sure your Airport Express is updated to the latest firmware. Up until recently the Airport Express would get an IPv6 address for itself but would not issue them via DCHP which is why you needed to do it manually. This may be what's happening for you. The Airport Extreme only gained DHCP support for this at the last firmware update so I'd assume the ...


1

It appears that my Client IPv4 (as configured on the TunnelBroker website) had gone out of date. I was unaware my IP address had changed since after changing ISPs some time ago. But I figured it out. Bring on the v6!



Only top voted, non community-wiki answers of a minimum length are eligible