BBC iPlayer buffering

[zoesdad1]

Hi, 

I've had issues with iPlayer buffering for some time, but I have put this down to the feed from the Hub to the V6 box. This was through an aging Devolo 500Mbps Powerline network. I have to use Powerline as Wifi doesn't work as the distance from Hub to V6 is quite large and has a couple of walls in between. 

I've replaced the Devolo with a new Devolo Magic 2, and thought that I had fixed the issue, but sadly not. Buffering again last night, which seemed to coincide with Wifi dropouts (my wife was Facebooking at the time on her tablet which is connected to the 5G Wireless network. The Wifi dropouts are only short-lived, but when iPlayer buffering stopped it returned the programme I was watching to the start. 

Running a Ping on the Hub this morning targeting BBC.CO.UK gave vastly different packet return times (ranging from 10 ms to 11330 ms) and a consistent 60% packet loss. 

Any assistance in sorting this would be gratefully received. 

[gary_dexter]

Please post the network, upstream and downstream logs from the hubs admin pages back here as text

[zoesdad1]

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	219000000	1.7	38	256 qam	11
2	203000000	2	37	256 qam	9
3	211000000	1.9	37	256 qam	10
4	227000000	1.4	37	256 qam	12
5	235000000	1.2	37	256 qam	13
6	243000000	1.2	37	256 qam	14
7	251000000	1.2	38	256 qam	15
8	259000000	1	37	256 qam	16
9	267000000	1	37	256 qam	17
10	275000000	1.2	38	256 qam	18
11	283000000	1.7	38	256 qam	19
12	291000000	2	37	256 qam	20
13	299000000	2.5	37	256 qam	21
14	307000000	2.5	38	256 qam	22
15	315000000	2.4	37	256 qam	23
16	323000000	1.9	37	256 qam	24
17	331000000	1.5	37	256 qam	25
18	339000000	1.7	38	256 qam	26
19	347000000	1.7	37	256 qam	27
20	355000000	1.9	38	256 qam	28
21	363000000	1.9	38	256 qam	29
22	371000000	1.7	38	256 qam	30
23	379000000	1.5	37	256 qam	31
24	387000000	1.2	38	256 qam	32

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	38.6	5	0
2	Locked	37.6	3	0
3	Locked	37.3	4	0
4	Locked	37.3	6	0
5	Locked	37.6	6	0
6	Locked	37.6	7	0
7	Locked	38.6	4	0
8	Locked	37.6	7	0
9	Locked	37.6	7	0
10	Locked	38.6	6	0
11	Locked	38.6	6	0
12	Locked	37.6	6	0
13	Locked	37.6	6	0
14	Locked	38.9	4	0
15	Locked	37.6	3	0
16	Locked	37.3	6	0
17	Locked	37.6	0	0
18	Locked	38.6	6	0
19	Locked	37.6	8	0
20	Locked	38.6	5	0
21	Locked	38.6	4	0
22	Locked	38.6	6	0
23	Locked	37.6	5	0
24	Locked	38.9	0	0

[zoesdad1]

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	32600000	35.8	5120	64 qam	5
2	39400039	35.8	5120	64 qam	4
3	46200004	36	5120	64 qam	3
4	53700000	36.5	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

[zoesdad1]

Time Priority Description

11/01/2022 08:59:57	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2022 20:29:19	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2022 15:33:5	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2022 00:23:26	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 17:53:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/01/2022 22:16:32	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/01/2022 16:45:18	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/01/2022 21:53:44	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 05:53:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/01/2022 14:47:6	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2022 17:53:6	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2021 01:02:41	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 05:53:6	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/12/2021 22:08:54	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 23:12:39	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 17:53:6	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2021 15:16:54	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2021 05:53:6	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/12/2021 17:22:57	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2021 16:55:21	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[jbrennand]

Stats are all pretty spot on.

If you look in the V6 Settings>Network - what does it report about the quality of theconnection?

Wasnt clear... are you connecting to the Devolo to the V6 on its wifi or running a short ethernet cable from it to the V6. If wifi can you try it on ethernet?

[zoesdad1]

HI, 

V6 seems to be happy with the network connection, although there doesn't seem to be a lot of information available to the end-user.

The network connection is Ethernet from hub to Devolo input,  then ethernet from Devolo output to TV box. No WiFi involved. 

[Adduxi]

Are the Devolo plugs on the same fused power circuit? Or are they crossing the consumer unit? 

[zoesdad1]

As far as I have been able to determine, both the sockets are fed from the same fuse in the consumer unit. 

[jbrennand]

Have you tried it on the Devlo wifi connection ?

All I can suggest is buying a 20-50 meter run of Cat5e cable ((less than a tenner) and plug the V6 into the Hub using that. Just trail the cable up stairs, over carpet etc for an hour or two and then test the iPlayer and other online content that way. When done just roll it up and put it into your bits drawer until needed again.

If that works fine, then at least you know that the issue lays firmly in the Devolo/mains circuit side of the connection. If it doesn't then its a VM equipment issue - V6/Hub or connection issue