Hello,
most of the normal users, like me, have an internet connection with a
dynamic ip-address (DSL with NAT etc.) and not a
static ip-address, which would be much easier to handle, but also is much more expensive. The tunnel works als long as the dynamic ip-address doesn´t change. The people at Sixxs use the programm aiccu for solving this problem, with -heartbeats- and -aiya- etc.
This solution is not possible for HE, as far as I know.
During the last days I set up a tunnel with HE and a subnet, all works fine. Thanks to HE for the free service.
The thing that remained to be solved was the automatic update of the tunnel endpoint, the dynamic ip-address. The solution I found is as follows (shell script/Debian):
#######################################################################
# Update des HE (Hurricane Electric) ipv6-Tunnels, wegen der dynamischen IP
#######################################################################
NEW_IP=`host freese.mx-host.de | grep -Eo '\<[[:digit:]]{1,3}(\.[[:digit:]]{1,3}){3}\>'`
wget --no-check-certificate -T10 -a$LOG - "
https://ipv4.tunnelbroker.net/ipv4_end.php?ipv4b=$NEW_IP&pass=YOUR_MD5_PASS&user_id=YOUR_HE_ID
&tunnel_id=YOUR_HE_TUNNELID"
---------------------------------------------------------------
where:the wget option -a$LOG means my own logfile, you take your own or remove the option
the https:// string is as suggested by HE for update
and NEW_IP, the shell variable gets the new (dynamic) ip-address from one of my Dyn.DNS providers.
The general solution could be, for other users:
NEW_IP=`wget http://whatismyip.org/ -q -O - | grep -Eo '\<[[:digit:]]{1,3}(\.[[:digit:]]{1,3}){3}\>'`You may run this script at startup oder as a -cron- job.