Packet loss on the Plusnet network
Thank you sir 
I'm not going to force a router reboot right now, since I'd like to monitor the packet loss (or more to the point, lack of packet loss) for at least 24hrs before risking changing anything
Thanks again, and cheers,
-- Neil
I'm not going to force a router reboot right now, since I'd like to monitor the packet loss (or more to the point, lack of packet loss) for at least 24hrs before risking changing anything
Thanks again, and cheers,
-- Neil
Everything continues to look good. I used VOIP for a good 4hrs last night, and it was perfectly ok too - for the 1st time in 2 weeks !!!
Overnight, as a test, I left a large download running to see how it coped, and again no problem. The odd packet loss - but only very occassionally, and I'd expect to see that on a saturated line.
As you suspected, the interleave request went through yesterday afternoon although it was cancelled. As I suspected, since the problem seemed to have fixed itself well before interleaving got switched back on, it made no difference to the packet loss problem - since there was no longer any to see It did, however, as is to be expected add 50% to my baseline ping and drop my downstream sync to 7,616,000. I'd appreciate it if fastpath could be re-enable now. What did surprise me was that the SNR margin increased by 2dB (I normally see 10-10.5dB and now it's at 12-12.5dB). Obviously both levels are fine, but I'm curious as to why enabling interleaving could change the SNR margin? Attenuation has also dropped from a normal 9.5-10dB to 9dB.
Thanks again for all your help Ben - I guess we'll never know for sure what was wrong, and why it cleared itself in the wee hours of Wednesday morning!!!
Overnight, as a test, I left a large download running to see how it coped, and again no problem. The odd packet loss - but only very occassionally, and I'd expect to see that on a saturated line.
As you suspected, the interleave request went through yesterday afternoon although it was cancelled. As I suspected, since the problem seemed to have fixed itself well before interleaving got switched back on, it made no difference to the packet loss problem - since there was no longer any to see
It did, however, as is to be expected add 50% to my baseline ping and drop my downstream sync to 7,616,000. I'd appreciate it if fastpath could be re-enable now. What did surprise me was that the SNR margin increased by 2dB (I normally see 10-10.5dB and now it's at 12-12.5dB). Obviously both levels are fine, but I'm curious as to why enabling interleaving could change the SNR margin? Attenuation has also dropped from a normal 9.5-10dB to 9dB.Thanks again for all your help Ben - I guess we'll never know for sure what was wrong, and why it cleared itself in the wee hours of Wednesday morning!!!
It looks like fastpath kicked in around 6am this morning.
Packet loss? What packet loss
Ping levels are low and stable, and the router is showing 8,128,000 DS again.
I'm convinced BT must have done something the other night - DS attenuation is staying @ 9dB, and it was always a couple of dB higher and SNR Margin is pretty steady @ 11dB whereas it was 10-10.5dB for as long as I remember. It's ofc possible it's a coincidence, but it seems very strange that I had 2 weeks of problems that just disappeared overnight, and now my line stats are slightly different.
But ho, hum - it doesn't matter; all that matters is that I have a nice, stable line back.
Thanks for all your efforts Ben.
Packet loss? What packet loss
Ping levels are low and stable, and the router is showing 8,128,000 DS again.
I'm convinced BT must have done something the other night - DS attenuation is staying @ 9dB, and it was always a couple of dB higher and SNR Margin is pretty steady @ 11dB whereas it was 10-10.5dB for as long as I remember. It's ofc possible it's a coincidence, but it seems very strange that I had 2 weeks of problems that just disappeared overnight, and now my line stats are slightly different.
But ho, hum - it doesn't matter; all that matters is that I have a nice, stable line back.
Thanks for all your efforts Ben.
Looks like the port was flexed (=switched off and on again!) which solved the problems. I'll close your ticket off, feel free to drop me a pm if you have any further problems