Setting up teredo tunneling pseudo interface properly

Hi,

I'm using (or trying to) Ipv6 with altbinz, and after enabling ipv6 via command line and using netsh interface ipv6 set teredo client, everything works beautifully for a few seconds/minutes, and then the teredo client goes back to being disconnected.
I can re-enable it, but the setting never sticks.

Here is a little history from enabled and working fine to disconnected with a "secondary server address unreachable" error.

netsh interface ipv6>show interface
Querying active state...

Idx Met MTU State Name
--- ---- ----- ------------ -----
6 0 1500 Disconnected Local Area Connection 2
5 2 1280 Connected Teredo Tunneling Pseudo-Interface
4 0 1500 Connected Wireless Network Connection
3 1 1280 Connected 6to4 Pseudo-Interface
2 1 1280 Connected Automatic Tunneling Pseudo-Interface
1 0 1500 Connected Loopback Pseudo-Interface

netsh interface ipv6>show teredo
Teredo Parameters
---------------------------------------------
Type : client
Server Name : default
Client Refresh Interval : default
Client Port : default
State : probe(cone)
Type : teredo client
Network : unmanaged
NAT : cone

netsh interface ipv6>show teredo
Teredo Parameters
---------------------------------------------
Type : client
Server Name : default
Client Refresh Interval : default
Client Port : default
State : probe(restricted)
Type : teredo client
Network : unmanaged
NAT : restricted

netsh interface ipv6>show teredo
Teredo Parameters
---------------------------------------------
Type : client
Server Name : default
Client Refresh Interval : default
Client Port : default
State : offline
Error : secondary server address unreachable

This whole set-up used to work perfectly until a few weeks ago, but now the settings just don't stick for more than a few minutes.
I'm still using the same D-Link 524 router and have not changed any settings.

If someone can help me figure out what I'm missing, I'd be grateful. All my searching has not resulted in resolving this issue.
I can't say I totally understand everything involved with ipv6, but I can follow instructions!

 

Seems I've got it solved by using the Gateway6 client.