What's new

ipv6 recipe for asuswrt-merlin via hurricane electric

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

i've set it up with your guide and everything worked out
had some issues with the password part.
but when i choose the tunnelkey as password it worked out.

only issue i got now is that i can't connect to my internal network anymore.
do i need to change something else to make this working again
 
I have found that sometimes wan-start runs before the wan is ready to go, causing the tunnel update to fail.

I added the following to verify the connection by pinging the HE server between defining the settings and updating the tunnel:


Code:
#**********************************
# pause until connection is ready #
#**********************************

#if ping test succeeds, log it and proceed to update tunnel.


if ping -c 1 "$HE_VERIFY_SERVER_IP" &>/dev/null

then

    echo " " >> "$STARTUP_SCRIPT_LOG_FILE"
    echo "Already Connected - $( date )" >> "$STARTUP_SCRIPT_LOG_FILE"

#if ping test failed, pause until connection is ready.

else
    i=0
    while [ $i -le 50 ]
    do
        if ping -c 1 "$HE_VERIFY_SERVER_IP" &>/dev/null
        then
            echo " " >> "$STARTUP_SCRIPT_LOG_FILE"
            echo "Now Connected, starting tunnel update - $( date )" >> "$STARTUP_SCRIPT_LOG_FILE"
            break
        fi
        echo >> "$STARTUP_SCRIPT_LOG_FILE"
        echo "Not Connected, - $( date )" >> "$STARTUP_SCRIPT_LOG_FILE"
        echo "connecting wait ..."

        sleep 15

    done
fi

Now the tunnel update on boot is more reliable.
 
Last edited:

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top