Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to set up an IPv6 tunnel through HE, using an Airport Extreme (7.6.1). I got it to work once, but have a real chicken and egg problem: I'm on a PPPoE internet connection, the Airport Express being the primary router/dialup device. Every single time it dials in, it receives a different IP address. I have set up an automated script on a machine that's permanently on, which will update HE with the current IPv4 address, but I'm running into timing issues. It seems the Airport Express only tries to establish the tunnel once after rebooting. If HE hasn't been updated by then (very likely), it will fail and apparently never try again. To make it try the IPv6 tunnel again, I need to reboot it, which makes it assume a different IP address etc etc.

Is there any solution to this conundrum? Can the Airport Express be persuaded to try reestablishing the tunnel without restarting it?

share|improve this question

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:

In summary you will need to configure ddclient with a helper script to extract your IPv4 public IP directly from the Apple router (not via default web mechanism) [see n1] and update the HE tunnel end-point (e.g.)

# /etc/ddclient.conf

daemon=300                              # check every 5 minutes
syslog=yes                              # log update msgs to syslog
#mail=root                              # mail all msgs to root
#mail-failure=root                      # mail failed update msgs to root
pid=/var/run/               # record PID in file.

# update tunnel end-point address
use=cmd, cmd=/opt/scripts/
<your-HE-nick>-<#tunnel>.tunnel.tserv<#num server>

Once your router reboots and/or and gets a new public DHCP lease, you HE tunnel will be temporarily down. Once ddclient runs and updates the HE tunnel end-point, your tunnel should come up. I've had this running for a while now, and it usually taken no more than x2 ddclient intervals (10 minutes) to get the tunnel back.



share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.