I'm looking up routers that do 'native IPv6 out of the box' - Seems D-Link were involved at the very beginning.
https://www.sixxs.net/wiki/Routers

https://www.cnet.com/news/top-5-ipv6-ready-wireless-...

Zyxel back in line - Result after configuration request!
http://postimg.org/image/570jezmnv/

Edit - Two mins later re-sync and back to square 1 - A total load of [censored] we have paid for!
http://postimg.org/image/vgllxs8l7/

Back to square one in more ways than one!
http://www.thinkbroadband.com/speedtest/results.html...

Don't think anyone can sort this line when on BTW!

Edited by professor973 (Sun 27-Nov-16 17:57:50)

In reply to a post by professor973:

I'm looking up routers that do 'native IPv6 out of the box' - Seems D-Link were involved at the very beginning.

One of the routers I tried while at IDNet was a D-Link. It kept crashing. Maybe not statistically significant but I still have hard feelings about that and I think it relates to the quality of support I experienced. I don't remember any details but I know that to this day (some four or five years later) I refuse to buy anything from D-Link.

Edited by Andrue (Sun 27-Nov-16 17:43:32)

That's OK, Just ordered a Fritzbox.

Notice the TP-Link TD-W9980 was mentioned earlier in the thread.

Some of us have been talking on the BT Community Forum recently about TP-LInk support for IPv6 in their modems/routers. The position seems to be that TP-Link devices don't support the /56 prefix delegated dynamic addresses used by BT and, I believe, most other UK ISPs. (I think Andrews & Arnold use /48 prefix.)

TP-Link have apparently acknowledged that their devices only support /64 prefix delegation. They've said that they won't be updating the TD-W9980 firmware to solve this problem. We're still trying to pin them down in relation to more recent models (e.g. Archer VR600 and VR2600).

So TP-Link devices don't currently look too promising if you're interested in IPv6 functionality.

p

Thanks prinknash .

A & A allocate a /48 to a customer, and a /64 within that per customer line. I'm no IPv6 expert yet, but that looks OK to me?

RobertoS - I'd be surprised if your IPv6 expertise didn't exceed mine!

I only mentioned A&A as an example of what I understood to be the practice of UK ISPs. The issue arose in the context of some BT Infinity customers trying, and failing, to get IPv6 connections using their TP-Link devices. Those who understand these things a lot better than I do have apparently established that TP-Link don't (currently?) support the necessary /56 prefix delegated dynamic addresses.

Personally, I'm still not sure how concerned I ought to be about having a modem/router that can't handle IPv6. Although it's obviously irritating if it says it can and then can't because it hasn't actually been tested against what UK ISPs provide.

p

In response to this post...

In reply to a post by RobertoS:

All I want is to run the tbb BQM on IPv6. I have tried setting two different routers as per AAISP instructions and the address still changes every few hours.

I'd like to know how you define the "first" address, which I think I have tried, and why you say on the LAN, not the WAN.

As has been said, different ISPs have different implementations.

My router gets a 2001:8B0:1111... address on it's WAN port and I've manually configured the LAN port to advertise my /64 prefix. I've statically configured the router LAN to be <My Prefix>::1

I think you can do the same in Network Setting>Home Netwok>LAN Setup (if I read the manual correctly?) Set LAN IPv6 Address to Static and enter an address within your allocation i.e Prefix::1 and then put your prefix address and length in the ULA IPv6 Address Setup boxes.

As I hinted, I'm no expert, and this may be nonsense!

[EDIT] I've just read the AAISP IPv6 support page and confirm the the last bytes of my WAN IP address are the same as my IPv4 IP address so, in my case, this would appear to be static. I guess it isn't for you?

Perhaps you can safely ignore me!

Edited by ferretuk (Fri 02-Dec-16 11:03:40)

Just to say I read your post a while ago but have been very busy. Thanks as well for switching to this thread.

I'll be working on the problem later, bearing in mind both your posts, but had already tried the AAISP pages you refer to plus others more hidden. I'm sure it can be solved, but might have to be something done at their end.

Setting the last parts to the hex equivalent of the IPv4 static WAN address doesn't seem to work for me, whatever I put preceding it. Depending on the router, it can show it in the connection settings after a reconnection but the actual is different - and changes at non-regular intervals .

I'll keep the thread updated of course.

Hope you get it sorted and that I haven't confused things.

I don't think you need to (or should) be making changes on the WAN side. It's the LAN that's yours, hence suggesting you statically configure the router LAN interface. Remember that all IPv6 addresses are public so pinging the LAN side (or even a statically configured device on your network) with the BQM gives the same information as pinging the WAN interface.

Edited by ferretuk (Fri 02-Dec-16 14:25:17)