Probably what is killing my zyXel and Fritz. Both run IPv6 initially and then die.

A setting I missed. It may be irrelevant but was picked up from the instructions for some other router.

When I entered the A:B:C:0:F:G:H:I address, (note I typo-omitted the :I at the end previously), I also set the Prefix length to 128. The whole string in other words.

In reply to a post by RobertoS:

Text
1 2	IPv6 Address. . . . . . . . . . . : A:B:C:0:F:G:H:I(Preferred) Temporary IPv6 Address. . . . . . : A:B:C:0:J:K:L:M(Preferred)

Both of these addresses point to your computer, not the router.

* IPv6 Address is your computer's static address, and is what you'd connect to (or point a DNS hostname to) if you were running a server on your machine. On some operating systems it is based on your network interface's MAC address, but on Windows (and the latest macOS) it is randomly generated on first connection to the network (so will change if you reinstall your OS).

* Temporary IPv6 Address is what your computer uses when it makes outbound connections. The temporary address changes regularly as a way of increasing privacy. Your computer might have more than one of these as it can keep old addresses around for established connections and take a new one for new connections.

Using IPv6 Address in the TBB BQM will work, but only when your PC is switched on and connected to your network.

Wrong.

As I have already pointed out.

See my IPv6 BQM - which has one or two breaks due to me experimenting as posted recently above. All my kit apart from the router was off between at least 4am and 9:20am. I don't know what the latency buidup was to ~6:35am, but it was external and caused a re-sync.

Fact!

The fact that the AAISP IPv6 setup isn't the same as whatever you have experienced is completely irrelevant to me. It is now working 24/7 quite independently of there being anything on the LAN.

Edited by RobertoS (Sun 04-Dec-16 16:16:37)

Re-reading your post i think i see what you've done.

You've managed to successfully bodge things by taking your Windows machine's static address and assigning it to your router. Windows should be smart enough to claim a different address when it sees the one it wants has been taken by something else.

It does begin to sound that way . Something like ferretuk was describing but very hard to follow.

I've also now turned on a second Windows machine which is wired to the router. That will help cross-diagnostic when I've had a bite to eat.

In theory I should be able to but a basically random set of hex into the last three of four entries and that should work? Though I tried that very early on, in no doubt a rubbish way, and it didn't take. I shall try it once I have shut my stomach up.

Any suggestions otherwise please? And sorry for getting ratty - it was two people telling me BQM wouldn't work when the computer was turned off that was so obviously untrue got to me.

Perhaps you could wait until I report back on what I try within the next hour , see if I can sort it myself.

Edit - Oh, the SLAAC IP address for this computer, (the one the listings are from), as shown by the router's network map is completely different again.

Edited by RobertoS (Sun 04-Dec-16 17:24:01)

Right - progress.

See in my sig. What I have done is not as per the AA instructions, as the vital one is ambiguous. In that they give a generic example with dummy entries for last two fields of the /64 prefix. I have used the full /64 prefix supplied, then codged up the second /64. The confusing bit is that the fourth field of the /64 prefix I have never seen used.

I think perhaps my final /64 should be ffff:0: as shown, then my IPv4 address converted - which I worked out a couple of days ago. Wondering whether or not to try it, or simply ask them tomorrow.

Even simpler, as any config changes I make can get lost if the push a firmware update, (obviously I expect I could request them to consolidate my changes into their master copy for me), would be simply to ascertain my true presumably static IPv6 WAN address for the router and use that for BQM. Just like a static IPv4.

Probably much of a muchness, though maybe more secure with what I have done.

???? I hope the "Dead" one is dead! Ahhhh - got it, pinging this computer now. (I haven't disabled it yet, so you can compare old and new). I'm going out for about half an hour so will turn it off and confirm.

Edited by RobertoS (Sun 04-Dec-16 19:27:22)

Just what I've been trying to say...

But I haven't needed to perform anything like the rigmarole that you suggested. Only one setting is needed - the change to a static rather than automatic address assignment. Finding the address to put in there was the problem - as I'm using the built-in modem I don't see the assigned WAN address.

And for sure I wasn't pinging my computer.

My very first contribution to this thread suggested that you assign a static address to your router. Subsequent posts have tried to explain why and to correct some if your apparent misunderstandings.

If this has appeared to be a rigmarole then I've failed and, frankly, I won't bother again!