Some problems with IPv6



  • Hi. First of all, I'm experimenting with pfSense 2.1 RELEASE on ALIX box.

    I experienced some problems regarding dynamic DNS after configuring an IPv6 Tunnel with HE.net

    I already had a dynamic DNS associated to a personal domain using HE DNS service and then created a tunnel. So I configured a dinamic DNS entry on pfSense to update the dynamic IP of the tunnel's client side.

    After configured all IPv6 stuff and make IPv6 work on my LAN, suddenly my WAN IP changed as usually (randomly) does with my ISP.

    The dynamic DNS entry configured for my tunnel succesfully updated the tunnel's IP but the dynamic DNS for the domain didn't update.

    The log entry said that the address metric is not valid for the configured protocol. May be is something wrong with the update routine after activating IPv6.

    I'm using a custom updater with Hurricane Electric because the HE.net updater entry on the dropbox didn't work (this is another problem) and the update URL is, as informed at dns.he.net:
    http://username:password@dyn.dns.he.net/nic/update?hostname=hostname&myip=%IP%
    It should respond "good %IP%" on success.

    Actually I solved the problem thanks to an advanced option on HE tunnel that makes the update to the hostname automatically after the tunnel's client IP changes. So the hostname's IP is also updated when pfSense updates the tunnel's IP.

    Another proble I have is that DHCP6/RA does not assing IPs to my hosts on the LAN side. Having followed the instructions on pfsense page without success. So I'm using static assigned IPv6 addresses.

    May be I'm doing wrong on some step, but theres not many options out there to test.

    Thank you and thanks to pfSense team…

    PS: I will post some updates on this topics



  • @muchacha_grande:

    I'm using a custom updater with Hurricane Electric because the HE.net updater entry on the dropbox didn't work (this is another problem) and the update URL is, as informed at dns.he.net:
    http://username:password@dyn.dns.he.net/nic/update?hostname=hostname&myip=%IP%
    It should respond "good %IP%" on success.

    Works fine here, for both v4 and v6. Note that "password" is not your dns.he.net password, but rather the hash for the domain you're updating ("DDNS" column in the dns.he.net web interface).

    That said, if you're using this for a tunnel broker IP, you should really be using the "HE.net Tunnel broker" mechanism, not the regular "HE.net" one.



  • You're right… sure I've made a mistake the first time I tried...

    But, there are still some updates problems. When my box reboots, for example, dynamic IP updates fail. So the tunnel doesn't work without my intervention.
    DNS updates fails two.

    Another message that appears and need acknowledge is: There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads {0}


Log in to reply