BT native IPv6

Has IPv6 been rolled out across the network yet?

I have been unable to obtain a prefix delegation, and have instead resorted to using a HE 6to4 tunnel.
My router (routerboard) sends the solicit request for a PD but gets no response at all.

My Hub 6 shows me as IPv6.

Mine did - when I had it a few weeks ago. I had 6 but only with the HH6

In reply to a post by Zarjaz:

My Hub 6 shows me as IPv6.

I think its hit and miss with BT.
I say this due to I had IPv6 enabled before the last automated reboot of my Smart Hub and now I don't have it, shown below:

Hub IPv6 status: Enabled
IPv6 network status: Disabled

IPv6 WAN details
Global unicast address: Not available
Global unicast prefix / length: Not available
Link local address: hidden
Remote link local address: hidden
DNS: Not available

I wish BT would make their minds up.

I normally do a manual reboot when it doesn't setup IPv6, but this time I haven't had the chance.

*** update ***
Well now after several reboots of my Smart Hub I still don't have IPv6, which sucks.

Paul

Edited by PaulKirby (Sun 02-Apr-17 01:29:45)

Well I just got a response from BT Care via Twitter:

Hi Paul

Sending a DM so I've more characters. This has been looked into and we've been advised - "IPv6 has been enabled on the majority of our network since 21st Oct 2016 and is enabled on our new Smart Hub. We are experiencing an intermittent fault where IPv6 is showing as disabled on the network and then reappearing. We are working to fix this. This will not affect your connectivity as an IPv4 address will continue to be available.�

So that's why it keeps disappearing and reappearing all the time.

From what I can see in my Smart Hub logs, when it works I can see DHCPv6 logs to do with Solicit, Advertise, Request, Confirmation of Request, Reply, now when it not working those logs are not to be seen.

So it might be an issue in BT's Network or it might be a Smart Hub issue.

*** update ***

I was told they have no fix date as yet, so this might take a while.

They also referred me to a post on the BT Community Forums:
https://community.bt.com/t5/Connected-Devices-Other/...

So they are aware of the issue.

Paul

Edited by PaulKirby (Sun 02-Apr-17 11:36:45)

Well, it's good to know that it's not just me! But, native IPv6 hasn't worked at all for me since I connected mid Feb.
I can't imagine I'd get far reporting this as a fault, as even if I got through to someone who understands that there is a difference between IPv4 and IPv6, the response would likely be something like "well you can still use the Internet because you have IPv4", which is true for the most part, but services are beginning to take advantage of IPv6 now, consoles etc.

Native IPv6 was one of the reasons I selected BT vs some other providers, so it is disappointing that it isn't working for me.

In reply to a post by LadFromWales85:

Well, it's good to know that it's not just me! But, native IPv6 hasn't worked at all for me since I connected mid Feb.
I can't imagine I'd get far reporting this as a fault, as even if I got through to someone who understands that there is a difference between IPv4 and IPv6, the response would likely be something like "well you can still use the Internet because you have IPv4", which is true for the most part, but services are beginning to take advantage of IPv6 now, consoles etc.

This is what BTCare said to me via Twitter, while this is true, it doesn't help me due to the software / game I am developing required IPv6 where I was working on that side of things.

So now I have to put that on hold and work on another section of it, which is fine.

The last time IPv6 was working was the last reboot which was on 06:26:01 27 Mar, sadly we had a power trip and IPv6 is now no longer working and I cannot see any DHCPv6 in the logs after the above date.

In reply to a post by LadFromWales85:

Native IPv6 was one of the reasons I selected BT vs some other providers, so it is disappointing that it isn't working for me.

Well we chose BT due to only 3 ISP's supplies FTTP for the home at the speed we wanted and BT was the cheapest.

We could of gone the business route and had more of a choice, but that would of cost even more.

Paul

Well this is interesting...

I have tried rebooting my Smart Hub several time over the last few days and still no IPv6 issued.
Anyway I just brought myself a FRITZ!Box 4040 Router, which is basically only a router and has no modem.

This comes with a 1Gbit WAN Port and 4 1Gbit Ethernet Ports and a couple of USB2 and USB3 ports and that's it.

Sadly this model isn't for the UK hence it only comes with the standard 2 pin European plug on the PSU.
Lucky I already had a FRITZ!Box 3390 ADSL/VDSL Modem / Router that came with a UK plug on the PSU, luckily it was the same voltage and polarity but with a higher power rating which helps.

Anyway after I configured everything up, turned off features I didn't want and nail it down as secure as possible, I noticed that IPv6 was working again, I was like BT must of fixed the issue, so I thought I would try the Smart Hub once again, sadly no IPv6, so a few more reboots and still no IPv6.

Connetced up the FRITZ 4040 and IPv6 was enabled, did several reboots etc and every time it had IPv6.

So from that conclusion I am thinking BT's IPv6 issue must be an intermittent Smart Hub issue that has a hissy fit with BT's DHCPv6 Servers.

I have stuck with the new 4040 due to its not sluggish at all even when connection is at full load which is good, it also comes with a great Wi-Fi Scanner to see what channels are in use and how many are using them.

This also means I can have the BQM running on my connection now where as before with BT's Hubs I haven't be able.

I might use the Smart Hub as a Wi-Fi point at the back of our home.

So overall its a win win

Paul

In reply to a post by PaulKirby:

So overall its a win win

But not much of a win for people who want IPv6 on BT without spending out on new kit.

I haven't seen IPv6 drop out once on my Sky connection with an SR102.

In reply to a post by Oliver341:

In reply to a post by PaulKirby:

So overall its a win win

But not much of a win for people who want IPv6 on BT without spending out on new kit.

Well I was holding off buying this, but due to needing IPv6 at the moment, I forked out £94, I am sure you can get it cheaper off ebay, but not knowing what plug came on the PSU I got it from Amazon, that way is an issue Amazon can deal with it.

In reply to a post by Oliver341:

I haven't seen IPv6 drop out once on my Sky connection with an SR102.

Well that's the issue there are people using the Smart Hub on a BT connection and IPv6 is fine, it was for me for a while, then it would just loose it, then it would come back and now it just doesn't want to work on my Smart Hub.

So it must be an intermittent compatibility issue between the two, that's all I can guess.

Like I have already said I think, I use to get DHCPv6 logs in my Smart Hub when it was working, but I am now no longer getting them no matter how many times I reboot the hub.

Now on the FRITZ!Box 4040 I can see in the logs it requesting for an IPv6 address from BT's DHCPv6 Servers on every reboot, so it seems to me its an issue with the DHCPv6 Client on the Smart Hubs at fault.

But yeah, my bother is with Zen for his FTTC connection and his IPv6 is working fine.

Paul

In reply to a post by PaulKirby:

Like I have already said I think, I use to get DHCPv6 logs in my Smart Hub when it was working, but I am now no longer getting them no matter how many times I reboot the hub.

More detailed connection logs would be one thing which would be nice on the SR102, since the logs are very basic like "WAN link UP" and "Connection UP" with no mention of how IPv6 is being provisioned. But since I've have no need to diagnose issues I suppose it's a moot point.

In reply to a post by Oliver341:

In reply to a post by PaulKirby:

Like I have already said I think, I use to get DHCPv6 logs in my Smart Hub when it was working, but I am now no longer getting them no matter how many times I reboot the hub.

More detailed connection logs would be one thing which would be nice on the SR102, since the logs are very basic like "WAN link UP" and "Connection UP" with no mention of how IPv6 is being provisioned. But since I've have no need to diagnose issues I suppose it's a moot point.

Well I never even seen any IPv6 logs on the Smart Hub until I exported the whole logs from it and then viewed it and saw these lines which was when IPv6 was last working (bottom up):

06:26:01 27 Mar. BR_LAN:DHCPv6 message : Reply LAN DHCPv6 Client: fe80::#:#:#:#
06:26:00 27 Mar. BR_LAN:DHCPv6 Confirmation of Request 
06:26:00 27 Mar. BR_LAN:DHCPv6 message : Request LAN DHCPv6 Client: fe80::#:#:#:#
06:26:00 27 Mar. BR_LAN:DHCPv6 message : Advertise LAN DHCPv6 Client: fe80::#:#:#:#
06:26:00 27 Mar. BR_LAN:DHCPv6 message : Solicit LAN DHCPv6 Client: fe80::#:#:#:#

Sadly our power tripped a few days later and IPv6 no longer worked on my Smart Hub.

Here is the logs from the 4040, granted its not much detail.

� 07.04.17 03:53:20 IPv6 prefix obtained successfully. New prefix: 2a00:#:#:#::/56
� 07.04.17 03:53:20 IPv6 Internet connection established successfully. IP address: 2a00:#:#:#:#:#:#:#
� 07.04.17 03:53:15 Internet connection established successfully. IP address: 86.140.x.x, DNS server: 217.32.171.21 and 213.120.234.62, gateway: 217.32.x.x, broadband PoP: bras-red5.l-ste-B22241507#####

And also the following from the Overview Page:

Internet IPv4, connected since 07.04.2017, 03:53 o'clock
         IPv4 address: 86.140.x.x
Internet IPv6, connected since 07.04.2017, 03:53 o'clock
         IPv6 address: 2a00:x:x:x:x:x:x:x

Here is a traceroute back from TBB to me:

#    Host                          Sent  Recvd  Best  Avg  Worst
1    2a02:68:85a3::ffff            15    15     0ms   11ms 130ms
2    po4-31.bdr-rt3.thdo.ncuk.net  15    15     0ms   1ms  10ms
3    lonap.he.net                  15    15     0ms   3ms  11ms
4    10ge2-9.core1.lon2.he.net     15    15     0ms   6ms  14ms
5    2001:7f8:4::1518:1            15    15     1ms   1ms  4ms
6    2a00:2000:2066::4b            15    15     1ms   1ms  2ms
7    2a00:2380:c::1d1              15    15     1ms   2ms  2ms
8    2a00:2380:300c:1001::47       15    15     1ms   2ms  2ms
9    2a00:23a0:1:4::2              15    15     1ms   2ms  2ms
10   2a00:23a0:1:7::2              15    15     2ms   2ms  3ms
11   2a00:x::x:x:e                 15    15     1ms   10ms 70ms
12   2a00:x::x:x:5                 15    15     1ms   2ms  2ms

I was shocked on the latency.

Sadly I still cannot get any connection stats due to its only a router connected via the WAN, but why would I need to see those, also would there even be connection stats for FTTP?
TBH I don't really know.

Paul