IPv6 on a TP-Link VR400 router

[#1]

@Jaggies I hope this is of some help - it's how I've set up my VR400 for IPv6 and it seems to work.

Advanced > Network >Internet, modify the connection as below:

(As I'm on full fibre, your page may look slightly different but I believe that most of the settings are the same.

Then in LAN settings IPv6, I have these settings:

I did not do anything with IPv6, tunnel left if not enabled.

My status page for IPv6 now looks as below:

These settings seem to allocate IPv6 addresses to the hosts on my LAN.

There does not seem to be any way of seeing what addresses have been allocated from the router (as there is for IPv4 addresses that have been given out using DHCP) but that is the same on my other router.

I've not found a way to log into the router using IPv6, again that is the same for my other TP-Link router.

My test-ipv6.com result is as follows:

[#2]

---

@IMM wrote:

There does not seem to be any way of seeing what addresses have been allocated from the router (as there is for IPv4 addresses that have been given out using DHCP) but that is the same on my other router.

---

That'll be due to you have RADVD enabled as to the router isn't actually handing out any addresses but merely a prefix against which clients can then generate their own addresses as they see fit. If you enabled DHCPv6 you'd likely then get a table of what addresses were allocated because that is what will have happened.

[#3]

@MJN 

Thanks. I did wonder whether it was something like that.

[#4]

If you enabled DHCPv6 you'd likely then get a table of what addresses were allocated

@MJN my tests seemed to show that Android clients still insisted on using SLAAC/RADVD even if a DHCPv6 server was available, so their addresses dont show in the DHCPv6 table

[#5]

---

@MJN my tests seemed to show that Android clients still insisted on using SLAAC/RADVD even if a DHCPv6 server was available, so their addresses dont show in the DHCPv6 table

---

Yeah, that's an 'Android-ism' as Google don't really believe in DHCPv6 being a valid approach to address assignment hence it doesn't currently implement it. There's a 13 year old issue on this which unfortunately remains marked as Won't Fix (Intended Behaviour).

[#6]

Thanks. Only difference I can see at a quick glance is that I am using DHCPv6 Server.
I'll give the other option a try at some point, but I'm of the firm opinion, "if it ain't broke..."
Either "...don't fix it"
Or "hit it with a hammer until it breaks, then you can get a new one..."