Lost IPv6 capability

[#1]

@Andy
My TBB v6 address and PN v6 addresses match.
I am going to try a bit of gateway hopping, currently on pcl-ag06.

[#2]

Gateway hopping did not reveal anything interesting, at least to me.
My TBB IPv6 graph remained red throughout.
test-ipv6.com - 10/10: pcl-ag06, pcl-ag07, ptn-ag02, ptw-ag01
test-ipv6.com -  0/10: pcl-bng03, pcl-bng04, ptw-bng02

[#3]

my guess still is that you not pinging the right ip, make sure you ping the router ip not pc, your pc ip changes unless you set it static due to the privacy stuff.

[#4]

Then why do I not get an IP address in the router, and why does none of three detectors sites pick up that I have an IP address? Why does the router log have two tries at getting one, report failure each time, then give up?
The ping loss is not down to an incorrect address. It is down to not being allocated one. I earlier gave two examples of IPv6 addresses that work with the BQM. I have many more.

[#5]

@Pete and jelv
Currently "You are currently connected to gateway pcl-ag06"
Current IPv6 BQM.
BQM set up ending in "fe33:c0a8"
Current IP address ends "fa19:9555"
So that's all hunky-dory at the moment except for the latency. Even that doesn't bother me too much as long as it doesn't translate into multi-secon page loads. At the moment, on a test of half a dozen, all OK.
@Pete - I think you may have the BQM set of for an incorrect address, as has been suggested for me. We know bngs don't work, but my problem was with any gateway. Next time I get a gateway change for some reason I shall see what happens. To check your current IP address try this link and set up a ping monitor on that. As long as you aren't on a bgn. Because the first 4 groups don't change a BQM should continue working when the last four change.

[#6]

Next interesting point. See tbb thread about ~1Mbps ipv6 download with IPv4 fine.

[#7]

bgn gateways seem to have had a problem with their IPv6 setup ever since they were introduced. I always change to a non bgn gateway if I end up on one.
I checked the IPv6 address of my router by telneting into it and running ifconfig. The IPv6 address it gave me agrees with the address being monitored by the BQM.
I have set up a BQM as advised, it is also red.

I think that something at the Plusnet end was altered at  00:55 30 Jan 2015. It needs a member of staff to comment.
My speeds from http://ipv6-test.com/speedtest are:  IPv4 53.8 Mbit/s :), IPv6 715 Kbit/s
Pete

[#8]

I just ran the test and got 63.5 for ipv4 and 61.4 for ipv6.
My PPP session has been up for 12 days tho, so I wonder if this only affects new ppp sessions.
Also I have occasionally in the past had really bad ipv6 speeds (and more recently also ipv4) which always got fixed by hopping gateways.

By the way check my ipv6 tbb graph in sig, it has peak time packetloss (not present on ipv4 graph).  So I am amazed I managed that speedtest result.

[#9]

Hi
Has anyone else done a PPP reconnection since Saturday and had (or not had) the same issue?

[#10]

Quote

DSL Connection Uptime: 2 days, 11:59:17 Bandwidth (Up/Down) [kbps/kbps]: 832 / 8,128 Data Transferred (Sent/Received) [MB/GB]: 378.77 / 1.23

My IPv6 is OK - note I'm on IPSec.

[#11]

If it is of any use here are the results from:
http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-ping.php
IPv6 Ping Output:
PING 2a02:16c8:2000:b00:XXXX:XXXX:XXXX:XXXX(2a02:16c8:2000:b00:XXXX:XXXX:XXXX:XXXX) 32 data bytes
--- 2a02:16c8:2000:b00:XXXX:XXXX:XXXX:XXXX ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3009ms
---- Finished ------
If the result shows nothing, the host or IP is most likely not an IPv6 reachable host or IP!

http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-traceroute.php
TraceRoute IPv6 Output:
traceroute to 2a02:16c8:2000:b00:XXXX:XXXX:XXXX:XXXX (2a02:16c8:2000:b00:XXXX:XXXX:XXXX:XXXX), 30 hops max, 40 byte packets
1  2a02:348:82::1 (2a02:348:82::1)  5.514 ms  7.466 ms  5.441 ms
2  xl-internetservices.nl.ip6.jointtransit.nl (2a02:10:0:1::e:3)  7.596 ms  7.570 ms  7.575 ms
3  telehouse-north.ip6.openpeering.nl (2a02:10:1:1::3)  19.547 ms  19.275 ms  19.481 ms
4  2001:7f8:4::1ad7:1 (2001:7f8:4::1ad7:1)  7.990 ms  7.918 ms  8.233 ms
5  2a02:16c8:1:2::7 (2a02:16c8:1:2::7)  8.196 ms  8.145 ms  8.110 ms
6  2a02:16c8:1:2::17 (2a02:16c8:1:2::17)  8.404 ms  8.653 ms  8.336 ms
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
---- Finished ------
Finished!

[#12]

Quote from: jelv

My IPv6 is OK - note I'm on IPSec.

I assume you mean IPSC?  The thought I was having shouldn't be effected by IPSC/WBC. 

[#13]

Yes I did mean that.

[#14]

Quote from: paulmh5

Has anyone else done a PPP reconnection since Saturday and had (or not had) the same issue?

Hi Paul,
Everything running well at the moment since I got onto pcl-ag06 on Tuesday except the latency shown on my BQM is poor. My norm is 12-14ms. (I have 19 logged changes of the form:-
03/02/15 13:30 pcl-ag06 (at last). 20ms but snappy.
31/01/15 12:30 ptn-ag01 12ms (V laggy)
20/01/15 13:30 ptn-ag04 12ms
20/01/15 00:30 pcl-bng03 15ms).
Browsing is snappy however, so I'm not going to mess for now. Other things to worry about :).

[#15]

At least its working again for you