He.net dynamic dns issue

jimp

AFAIK the he.net dyndns type is for their dyndns service, not for updating an ipv6 tunnel endpoint IP. I'd have to look the code over to double check though.

bardelot

@jimp:

AFAIK the he.net dyndns type is for their dyndns service, not for updating an ipv6 tunnel endpoint IP. I'd have to look the code over to double check though.

They also have an interface to update the tunnel endpoint IP.


Usage: https://ipv4.tunnelbroker.net/ipv4_end.php?ip=IPV4ADDR&pass=MD5PASS&apikey=USERID&tid=TUNNELID
 -or-: https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID (auto-detect IP)
       https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID&ip=IPV4ADDR

IPV4ADDR: Your IPv4 endpoint.  Set to AUTO to determine your IP based on the IP you requested this page from.  Previously passed as ipv4b.
MD5PASS : The MD5 hash of your password.  You may be able to 'echo -n YOURPASSWORD | md5sum' to produce the MD5 hash of your password.
USERID  : The UserID shown on the main page of tunnelbroker.net when you log in.  Previously referred to as user_id.
TUNNELID: The ID of the tunnel you're updating the endpoint on.  This can be found on the tunnel information page.  Previously referred to as the Global Tunnel ID / tunnel_id.

jimp

I meant the he.net dyndns type in our code, not on their servers :-) The one in our code only goes to "https://dyn.dns.he.net/nic/update"

Though that is awesome that they have the update there. Last I saw they had some clunky perl script that did a POST to the tunnelbroker site. It should be possible to code up an update type for that rather easily then.

jimp

smacks the easy button

https://github.com/smos/pfsense-ipv6/commit/38a481adc8179b1df06faf0e7fcc08a51a6de53e

Cino

love the easy button!!

iFloris

awesome, thanks jimp!

singerie

Thanks jimp ! ;D

plinss

This isn't working for me. System log lists:
php: /services_dyndns_edit.php: phpDynDNS: (Error) Bad Request - Missing/Invalid Parameters.

Looking at the code in the commit above it seems that maybe HE changed the parameters they're expecting. I have this working in a script (on my desktop), this is what I'm using:
https://ipv4.tunnelbroker.net/ipv4_end.php?ipv4b=$NEW_IP&pass=$HEPASS&user_id=$HEUSER&tunnel_id=$HETUNNEL

Where $HEUSER is the user ID from the HE web page (not the username I log in to the site with) and $HEPASS is and MD5 hash of my HE web page login password.

jimp

Still updating and working fine for me.

The settings in the GUI are:
Hostname: tunnel id
Username: he.net username
Password: he.net password

According to their spec, your way works too.

http://ipv4.tunnelbroker.net/ipv4_end.php

We use the https method with basic auth and tid (middle choice here)

Usage: https://ipv4.tunnelbroker.net/ipv4_end.php?ip=IPV4ADDR&pass=MD5PASS&apikey=USERID&tid=TUNNELID
 -or-: https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID (auto-detect IP)
       https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID&ip=IPV4ADDR

IPV4ADDR: Your IPv4 endpoint.  Set to AUTO to determine your IP based on the IP you requested this page from.  Previously passed as ipv4b.
MD5PASS : The MD5 hash of your password.  You may be able to 'echo -n YOURPASSWORD | md5sum' to produce the MD5 hash of your password.
USERID  : The UserID shown on the main page of tunnelbroker.net when you log in.  Previously referred to as user_id.
TUNNELID: The ID of the tunnel you're updating the endpoint on.  This can be found on the tunnel information page.  Previously referred to as the Global Tunnel ID / tunnel_id.

The following parameters are only usable when accessing this script over https.
USERNAME: Your tunnelbroker.net username.
PASSWORD: Your tunnelbroker.net password.

The legacy parameter names will continue to work for the forseable future.  Naming of them changed to be more in line with industry convention and their roles.

plinss

Ah, thanks jimp! I was using the userid from the other method instead of my username. Works now.