What is the ipv6 address of my router

I have just moved to AA, and everything went smoothly apart from my BMQ.
Ipv4 is fine, but ipv6 is totally red. I am using the Fritz!Box 7530 that was working fine with Zen.

I spoke to AA support who said that they had never heard of the Fritz!Box, and had no idea what the ip address of the router is, and said that the problem must lie with ThinkBroadband as I can use ipv6 from PCs on my network.

With Zen, the ipv6 address of the router was the /64 allocation with ::1 appended, but doing the same with my AA /64 allocation doesn't work.

Hi

If you login to the fritzbox and go to internet, then online manager, doesnt that show its ipv6 address, mine's showing IPv6 address: 2001:8b0:1613:xxxx:xxxx:xxxx:xxxx:xxxx/64
I am using mine is access point mode rather than routing so may be different.

If your ip4 address works I should stick with that. I have a static ip4 address from Idnet, but because they provide an ip6 connection, my ip4 address does not work in the BQM (but I can host a web site off it!).

On the Fritzbox, the ip6 address for the router is on settings->Internet->online monitor under ip6 details. Unfortunately it appears to change every couple of months (as far as I can tell static ip6 addresses are quite rare). Easiest option is to use dynamic dns with a provider such as duckdns. Duckdns specific instructions are on the AVM site:
https://en.avm.de/service/knowledge-base/dok/FRITZ-B...

down under section 3.

Other option is to use ddns with something like a synology nas drive.

If using the Fritzbox, ignore the hanging blood on the BQM , it’s something to do with their dos hacking protection.

https://support.aa.net.uk/Category:IPv6 might be useful though they have their CQM anyway.

I don't have a Fritz!box, but if you can find out what your router's IPv6 address is on its LAN interface, that should work as a target from the outside too.

Note that routers don't actually need a globally-routable (public) IPv6 address on the WAN side. The router can get by with just a link-local address.

So whilst in the old days an ISP might have allocated a /64 for the point-to-point segment, this usually doesn't happen any more. With both Cerberus and Aquiss, they just point the whole /56 down the PPPoE session, and how you use it or assign it is up to you.

However, if you want to be able to login to the router and send IPv6 pings *from* the router (or DNS queries), then it should have a public IPv6 on the WAN side. I just configure the same ::1 address as one of my LAN side networks.

In reply to a post by DrBob:

IUnfortunately it appears to change every couple of months (as far as I can tell static ip6 addresses are quite rare).

Each ISP I've had with IPv6 has been static along with the IPv4 static address. With IPv6 though it is the subnet that is static, not necessarily the whole IPv6 address, and we can choose to use random addresses from that subnet and then throw them away after a day never to be used again (which is what most devices do by default for privacy and because there are trillions allocated to us we can just waste them), or we make them stick, that is our choice. IPv4 when static, we get just one address, with IPv6 we get a static subnet not a static IP address. IPv6 is a completely different way of thinking as the numbers are so huge. For example with IPv6 on A&A we actually get 65,536 subnets, with each subnet having 18,446,744,073,709,551,616 IP addresses.

In reply to a post by ukwiz:

I have just moved to AA, and everything went smoothly apart from my BMQ.
Ipv4 is fine, but ipv6 is totally red. I am using the Fritz!Box 7530 that was working fine with Zen.

I spoke to AA support who said that they had never heard of the Fritz!Box, and had no idea what the ip address of the router is, and said that the problem must lie with ThinkBroadband as I can use ipv6 from PCs on my network.

With Zen, the ipv6 address of the router was the /64 allocation with ::1 appended, but doing the same with my AA /64 allocation doesn't work.

Try doing a traceroute to say the BBC.co.uk, it should default to IPv6, and the first hop should be your gateway on the router. This address may be pingable and will be part of your allocation. However the Fritzbox may have that firewalled so you would need to see if its possible to add a rule to allow it to respond to pings, ideally you would make the rule to work only with Thinkbroadbands IP addresses. I'm not sure on how you do this with a Fritzbox.

In reply to a post by E300:

Try doing a traceroute to say the BBC.co.uk, it should default to IPv6

Be careful there. "bbc.co.uk" does indeed have IPv6 - but all that server does is issue a redirect to "www.bbc.co.uk", which does *not* have IPv6.

In short, BBC does not support IPv6 at all, apart from this dummy redirector, so you'd be better off choosing a different site that does.

The Google DNS service on 2001:4860:4860::8888 is the equivalent of 8.8.8.8 on IPv4, and that's a safe bet.

In reply to a post by E300:

and the first hop should be your gateway on the router. This address may be pingable and will be part of your allocation.

Unless it starts with fe80: in which case it's a link-local address. Globally-routable addresses start with 2xxx: or 3xxx:

I went through all this and although it sounds quite complicated it is actually quite easy, at least on my Asus AC88U router. First of all according to AAISP:

The WAN we assign is static - it's based on the IPv4 WAN address.
This WAN address is assigned by DHCPv6 from our side.

The IPv6 number assigned to your router is of the form:
2001:8b0:1111:1111:0:ffff:[your IPv4 WAN in HEX]

So all you need to do is convert your fixed IPv4 number to two pairs of hex numbers. I.e if your Ip number is 81.2.76.213 then convert each number to hex, which in this case would be

81 -> 51
2 -> 02
76 -> 4C
213 -> D5

So, for your IPv6 Thinkbroadband IPv6 BQM 2001:8b0:1111:1111:0:ffff:5102:4CD5

My Router is set for Native IPv6 and I can't help with any router other than ASUS

You may find this decimal to hex converter useful
https://www.binaryhexconverter.com/decimal-to-hex-co...

I hope this helps

Edited by Adrian (Thu 07-Mar-24 16:04:24)