cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Aspiring Contributor
1,135 Views
Message 1 of 15

Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

I have a PfSense router sitting beind a Draytek Vigor 130 which seems to work pretty well.

The only weird thing is that my IPTV WAN Sub interface seems to indicate its using in excess of 6MB when streaming UltraHD.

From what i can tell it should only require 45mbps or 5.625 MB/s.

I just wondered what stats you see?

0 Ratings
Reply
14 REPLIES 14
Highlighted
BT TV Expert
1,095 Views
Message 2 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

The BT Sport 4k channel uses 30Mbit/s or around 3.6Mbytes/s. 

 If the box is recording an HD channel at the same time that adds 9 to 14Mbit/s depending on the channel.

Note, if the router doesn't support IGMP snooping, or if the setting is disabled in the router, then it will broadcast all the IPTV multicast traffic to every device, including every WiFi connected device which will swamp your network and probably stop WiFi working completely.

We've seen this problem quite often with customers using non-BT hubs although I'm not sure this is the problem here. 

0 Ratings
Reply
Highlighted
Aspiring Contributor
1,087 Views
Message 3 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

Yeah,

  That is definately not what i see, additionally, i asked around and if you see here:-

https://community.bt.com/t5/YouView-from-BT/Experiences-with-Draytek-Vigor-130-and-BT-TV/m-p/1878080... user Leebobs also has a similar experience even though he uses a completely different router (the Synology RT2600ac router).

"Streaming the England U21 in 4KHD now I am averaging about 7.30MB/s down which is 90-95% through the BT Box"

The strange thing is, if i switch to a normal HD channel i will get around 17mbps (the first bit watching Discovery HD) over the WAN link - pretty much bang on what i would expect. Not with UltraHD though - that saturates my 54mbps WAN link (The second peak - ~60mbps).

 BTTV.PNG

 Nothing is recording at that time.

IGMP snooping is on on the LAN, but this is the WAN link, not the LAN. Could this be an issue with the Draytek?

0 Ratings
Reply
Highlighted
BT TV Expert
1,078 Views
Message 4 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

You shouldn't see 17Mbit/s for Discovery HD. The IP bit rate for Discovery HD is only 8.6Mbit/s, so you're seeing double the data rate on HD channels which doesn't look right at all.

Using a non-BT Hub is not recommended for various reasons. In particular, the BT Hubs ensure that the IPTV multicast traffic is prioritised and also reduce the broadband  bit-rate to allow for the IPTV multicast bit-rate. Other hubs are unlikely to do this so you will see subtle problems and may experience broadband issues when streaming UHD.

Your best option, if you really want to use a third party router, is to connect it downstream of the BT Home Hub.

0 Ratings
Reply
Highlighted
Recognised Expert
1,068 Views
Message 5 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

Just a thought , is the ethernet cable from the router going direct to the Youview box or via a switch? If a switch & if that switch doesn't support IGMP snooping you'll get flooding which may or may not be an issue.

0 Ratings
Reply
Highlighted
Aspiring Contributor
1,056 Views
Message 6 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

Hi,

  I have adjusted my config for testing - i have a 3 port router. Port1 - WAN (Draytek), Port 2 - LAN, Port 3 - IPTV

The IPTV port is on a completely different subnet from the LAN, there is an ethernet cable from this port directly to the IPTV box, no wireless involved or switch involved.

I cannot see how we have i can have double the usage here as there is nothing else on that subnet to request it other than that box. IGMP snooping is now irrelevant as the IPTV is isolated on its own subnet.

I still see double what i expect.

I took a debug of the IGMP requests to / from source and dest - is this any help to you?

[2.4.4-DEVELOPMENT][admin@pfsense..co.uk]/root: igmpproxy -dvvvv /var/etc/igmpproxy.conf
Searching for config file at '/var/etc/igmpproxy.conf'
Config: Quick leave mode enabled.
Config: Got a phyint token.
Config: IF: Config for interface re2.
Config: IF: Got downstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 192.168.20.1/24.
Config: IF: Altnet: Parsed altnet to 192.168.20/24.
IF name : re2
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : e26000
Config: Got a phyint token.
Config: IF: Config for interface re0.
Config: IF: Got upstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 224.0.0.0/4.
Config: IF: Altnet: Parsed altnet to 224/4.
Config: IF: Got altnet token 109.159.247.0/24.
Config: IF: Altnet: Parsed altnet to 109.159.247/24.
IF name : re0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 1
Allowednet ptr : e26010
Config: Got a phyint token.
Config: IF: Config for interface pppoe0.
Config: IF: Got disabled token.
IF name : pppoe0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface re1.
Config: IF: Got disabled token.
IF name : re1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface ovpnc1.
Config: IF: Got disabled token.
IF name : ovpnc1
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface re1.30.
Config: IF: Got disabled token.
IF name : re1.30
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface ovpns2.
Config: IF: Got disabled token.
IF name : ovpns2
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
buildIfVc: Interface re0 Addr: 10.20.30.40, Flags: 0xffff8843, Network: 10.20.30.40/32
buildIfVc: Interface re1 Addr: 192.168.254.1, Flags: 0xffff8943, Network: 192.168.254/24
buildIfVc: Interface re1 Addr: 10.10.10.1, Flags: 0xffff8943, Network: 10.10.10/24
buildIfVc: Interface re2 Addr: 192.168.20.1, Flags: 0xffff8843, Network: 192.168.20/24
buildIfVc: Interface lo0 Addr: 127.0.0.1, Flags: 0xffff8049, Network: 127/8
buildIfVc: Interface re1.30 Addr: 192.168.30.1, Flags: 0xffff8943, Network: 192.168.30/24
Found config for re0
Found config for re1
Found config for re1
Found config for re2
Found config for re1.30
Found upstrem IF #0, will assing as upstream Vif 2
adding VIF, Ix 0 Fl 0x0 IP 0x281e140a re0, Threshold: 1, Ratelimit: 0
        Network for [re0] : 10.20.30.40/32
        Network for [re0] : 224/4
        Network for [re0] : 109.159.247/24
adding VIF, Ix 1 Fl 0x0 IP 0x0114a8c0 re2, Threshold: 1, Ratelimit: 0
        Network for [re2] : 192.168.20/24
        Network for [re2] : 192.168.20/24
Got 262144 byte buffer size in 0 iterations
Joining all-routers group 224.0.0.2 on vif 192.168.20.1
joinMcGroup: 224.0.0.2 on re2
Joining all igmpv3 multicast routers group 224.0.0.22 on vif 192.168.20.1
joinMcGroup: 224.0.0.22 on re2
SENT Membership query   from 192.168.20.1    to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 1 (#0) - delay 10 secs
(Id:1, Time:10)
Created timeout 2 (#1) - delay 21 secs
(Id:1, Time:10)
(Id:2, Time:21)
RECV V2 member report   from 192.168.20.1    to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.1    to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV Membership query   from 192.168.20.1    to 224.0.0.1
The IGMP message was local multicast. Ignoring.
RECV V2 member report   from 192.168.20.6    to 234.81.132.201
Should insert group 234.81.132.201 (from: 192.168.20.6) to route table. Vif Ix : 1
No existing route for 234.81.132.201. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 234.81.132.201 on VIF #1
Joining group 234.81.132.201 upstream on IF address 10.20.30.40
joinMcGroup: 234.81.132.201 on re0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Dst: 234.81.132.201, Age:2, St: I, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
Route activate request from 109.159.247.201 to 234.81.132.201 on VIF[0]
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Adding MFC: 109.159.247.201 -> 234.81.132.201, InpVIf: 0

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.1    to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.1    to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.6    to 224.0.0.251
Should insert group 224.0.0.251 (from: 192.168.20.6) to route table. Vif Ix : 1
No existing route for 224.0.0.251. Create new.
Found existing routes. Find insert location.
Inserting after route 234.81.132.201
Inserted route table entry for 224.0.0.251 on VIF #1
Joining group 224.0.0.251 upstream on IF address 10.20.30.40
joinMcGroup: 224.0.0.251 on re0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:2, St: I, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
About to call timeout 1 (#0)
Aging routes in table.

Current routing table (Age active routes):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:1, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:1, St: I, OutVifs: 0x00000002
-----------------------------------------------------
RECV V2 member report   from 192.168.20.6    to 234.81.130.251
Should insert group 234.81.130.251 (from: 192.168.20.6) to route table. Vif Ix : 1
No existing route for 234.81.130.251. Create new.
Found existing routes. Find insert location.
Inserting after route 224.0.0.251
Inserted route table entry for 234.81.130.251 on VIF #1
Joining group 234.81.130.251 upstream on IF address 10.20.30.40
joinMcGroup: 234.81.130.251 on re0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:1, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:1, St: I, OutVifs: 0x00000002
#2: Dst: 234.81.130.251, Age:2, St: I, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
Route activate request from 109.159.247.251 to 234.81.130.251 on VIF[0]
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Adding MFC: 109.159.247.251 -> 234.81.130.251, InpVIf: 0

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:1, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:1, St: I, OutVifs: 0x00000002
#2: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:2, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV Membership query   from 0.0.0.0         to 224.0.0.1
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
The IGMP message was from myself. Ignoring.
The IGMP message was from myself. Ignoring.
RECV Membership query   from 0.0.0.0         to 224.0.0.1
RECV Membership query   from 192.168.2.1     to 224.0.0.1
About to call timeout 2 (#0)
SENT Membership query   from 192.168.20.1    to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 3 (#0) - delay 10 secs
(Id:3, Time:10)
Created timeout 4 (#1) - delay 21 secs
(Id:3, Time:10)
(Id:4, Time:21)
RECV Membership query   from 192.168.20.1    to 224.0.0.1
About to call timeout 3 (#0)
Aging routes in table.
Removing group 234.81.132.201. Died of old age.
Removed route entry for 234.81.132.201 from table.
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Removing MFC: 109.159.247.201 -> 234.81.132.201, InpVIf: 0
Leaving group 234.81.132.201 upstream on IF address 10.20.30.40
leaveMcGroup: 234.81.132.201 on re0

Current routing table (Remove route):
-----------------------------------------------------
#0: Dst: 224.0.0.251, Age:1, St: I, OutVifs: 0x00000002
#1: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:2, St: A, OutVifs: 0x00000002
-----------------------------------------------------
Removing group 224.0.0.251. Died of old age.
Removed route entry for 224.0.0.251 from table.
Leaving group 224.0.0.251 upstream on IF address 10.20.30.40
leaveMcGroup: 224.0.0.251 on re0

Current routing table (Remove route):
-----------------------------------------------------
#0: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:2, St: A, OutVifs: 0x00000002
-----------------------------------------------------

Current routing table (Age active routes):
-----------------------------------------------------
#0: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------
Route activate request from 109.159.247.201 to 234.81.132.201 on VIF[0]
No table entry for 234.81.132.201 [From: 109.159.247.201]. Inserting route.
No existing route for 234.81.132.201. Create new.
Found existing routes. Find insert location.
Inserting at beginning, before route 234.81.130.251
Inserted route table entry for 234.81.132.201 on VIF #-1
No downstream listeners for group 234.81.132.201. No join sent.

Current routing table (Insert Route):
-----------------------------------------------------
#0: Dst: 234.81.132.201, Age:2, St: I, OutVifs: 0x00000000
#1: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------

Current routing table (Activate Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000000
#1: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
Got leave message from 10.20.30.40 to 224.0.0.251. Starting last member detection.
The found if for 10.20.30.40 was not downstream. Ignoring leave request.
Got leave message from 10.20.30.40 to 234.81.132.201. Starting last member detection.
The found if for 10.20.30.40 was not downstream. Ignoring leave request.
RECV Membership query   from 192.168.2.1     to 224.0.0.251
RECV Membership query   from 192.168.2.1     to 234.81.132.201
RECV Membership query   from 192.168.2.1     to 234.81.132.201
RECV Membership query   from 192.168.2.1     to 224.0.0.251
RECV V2 member report   from 192.168.20.1    to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.6    to 234.81.132.201
Should insert group 234.81.132.201 (from: 192.168.20.6) to route table. Vif Ix : 1
Updated route entry for 234.81.132.201 on VIF #1
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Adding MFC: 109.159.247.201 -> 234.81.132.201, InpVIf: 0
Joining group 234.81.132.201 upstream on IF address 10.20.30.40
joinMcGroup: 234.81.132.201 on re0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.1    to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
Got leave message from 10.20.30.40 to 224.0.0.251. Starting last member detection.
The found if for 10.20.30.40 was not downstream. Ignoring leave request.
The IGMP message was from myself. Ignoring.
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.6    to 234.81.130.251
Should insert group 234.81.130.251 (from: 192.168.20.6) to route table. Vif Ix : 1
Updated route entry for 234.81.130.251 on VIF #1
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Adding MFC: 109.159.247.251 -> 234.81.130.251, InpVIf: 0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------
About to call timeout 4 (#0)
SENT Membership query   from 192.168.20.1    to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 5 (#0) - delay 10 secs
(Id:5, Time:10)
Created timeout 6 (#1) - delay 115 secs
(Id:5, Time:10)
(Id:6, Time:115)
RECV Membership query   from 192.168.20.1    to 224.0.0.1
The IGMP message was local multicast. Ignoring.
RECV V2 member report   from 192.168.20.6    to 224.0.0.251
Should insert group 224.0.0.251 (from: 192.168.20.6) to route table. Vif Ix : 1
No existing route for 224.0.0.251. Create new.
Found existing routes. Find insert location.
Inserting after route 234.81.132.201
Inserted route table entry for 224.0.0.251 on VIF #1
Joining group 224.0.0.251 upstream on IF address 10.20.30.40
joinMcGroup: 224.0.0.251 on re0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:2, St: I, OutVifs: 0x00000002
#2: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V3 member report   from 10.20.30.40     to 224.0.0.22
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.6    to 234.81.132.201
Should insert group 234.81.132.201 (from: 192.168.20.6) to route table. Vif Ix : 1
Updated route entry for 234.81.132.201 on VIF #1
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Adding MFC: 109.159.247.201 -> 234.81.132.201, InpVIf: 0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:2, St: I, OutVifs: 0x00000002
#2: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:1, St: A, OutVifs: 0x00000002
-----------------------------------------------------
About to call timeout 5 (#0)
Aging routes in table.

Current routing table (Age active routes):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:1, St: I, OutVifs: 0x00000002
#2: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:2, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V2 member report   from 192.168.20.1    to 224.0.0.2
The IGMP message was from myself. Ignoring.
RECV V2 member report   from 192.168.20.6    to 234.81.130.251
Should insert group 234.81.130.251 (from: 192.168.20.6) to route table. Vif Ix : 1
Updated route entry for 234.81.130.251 on VIF #1
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Adding MFC: 109.159.247.251 -> 234.81.130.251, InpVIf: 0

Current routing table (Insert Route):
-----------------------------------------------------
#0: Src0: 109.159.247.201, Dst: 234.81.132.201, Age:2, St: A, OutVifs: 0x00000002
#1: Dst: 224.0.0.251, Age:1, St: I, OutVifs: 0x00000002
#2: Src0: 109.159.247.251, Dst: 234.81.130.251, Age:2, St: A, OutVifs: 0x00000002
-----------------------------------------------------
RECV V2 member report   from 192.168.20.1    to 224.0.0.22
The IGMP message was from myself. Ignoring.
^Cselect() failure; Errno(4): Interrupted system call
Got a interrupt signal. Exiting.
clean handler called
Removing route entry for 234.81.132.201
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Removing MFC: 109.159.247.201 -> 234.81.132.201, InpVIf: 0
Leaving group 234.81.132.201 upstream on IF address 10.20.30.40
leaveMcGroup: 234.81.132.201 on re0
Removing route entry for 224.0.0.251
Leaving group 224.0.0.251 upstream on IF address 10.20.30.40
leaveMcGroup: 224.0.0.251 on re0
Removing route entry for 234.81.130.251
Vif bits : 0x00000002
Setting TTL for Vif 1 to 1
Removing MFC: 109.159.247.251 -> 234.81.130.251, InpVIf: 0
Leaving group 234.81.130.251 upstream on IF address 10.20.30.40
leaveMcGroup: 234.81.130.251 on re0
All routes removed. Routing table is empty.
Shutdown complete....
0 Ratings
Reply
Highlighted
Contributor
1,044 Views
Message 7 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

I can replicate these download rates when not using a BT Router, 4K entirely saturates the bandwidth with HD also using a substantial amount... Although I note that the DrayTek is BT SIN 498 MCT Approved

0 Ratings
Reply
Highlighted
Aspiring Contributor
1,032 Views
Message 8 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

Leebobs, can i ask you to check something - on your interface in that includes your IPTV / PPPoE WAN link.

Can you check that your 4k or HD channel definately uses as much as your graph reports.

The reason i ask is that i've noticed on PfSense that my Subinterface for the IPTV interface also appears to be showing the traffic traversing the WAN as well.

So, that means that whilst it looks like its using much more than it should be it could just be that your seeing IPTV traffic and then any WAN traffic lumped on top.

For example, i've notcied that on my system, addresses in the 234.x.x.x range are only using 13mbps but becuase something else is going on over my WAN link the graph is reporting a much higher rate of traffic even though im looking at my ITPV interface.

Saying that though i still see UltraHD traffic using 50mbps from its specific IP.

Host IP Bandwidth In Bandwidth Out

234.81.132.20150.89M Bits/sec0.00 Bits/sec

 

 
0 Ratings
Reply
Highlighted
BT TV Expert
1,014 Views
Message 9 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

AS2856 - good point about checking the graph meaning. If it is showing LAN + WAN traffic then that would explain the doubling you are seeing.

It's odd that you are seeing this though:

Host IP Bandwidth In Bandwidth Out

234.81.132.201 50.89M Bits/sec 0.00 Bits/sec

 

That is the correct multicast address for BT Sport 4K but it should be 30Mbit/s which I verified this morning using a stream analyser running on a BT VDSL line:

  Multicast streams  IP Bit Rates (Mbit/s) 
  Group            Min    Mean    Max 
  234.81.132.201   29.644 29.677 29.699

What make and model router are you using?

Your log above looks OK except that your router appears to be using a WAN IP address in the range 10.x.x.x which is specifically prohibited by BT SIN 503:

3.1.7 IGMP Operation - CP side

IGMP Membership Queries from the CP to the GEA network must avoid using an IP header source address in the same range as that used for GEA element management. Specifically address range 10.0.0.0/8 should be avoided.

 

 

 

 

 

Highlighted
Contributor
979 Views
Message 10 of 15

Re: Anyone with UltraHD and a Draytek 130 to Router combo on here? Looking for some info.

I have have BT Ultra HD with the Draytek130 router but use a TP-Link TL-R600VPN and never had a problem. The BT Ultra Box is plugged into my HP ProCurve 1400-24G 24 Port Gigabit Ethernet Switch - J9078A which socket 1 is plugged directly to the TP-Link VPN router.

I was initially concerned as i had come across people in the forums with issues and so made sure i got a router with IGMP but ive never turned this on and never had a problem in the 8 months ive been using this system. 

Juat as a further note, I group my devices into specific IP ranges, The router gateway is 192.168.1.1 and keep my servers in the range upto .10  streaming boxes .70 etc etc.

The BTHub 6 i had was not fit for purpose and had more issues with that then with the system i have now, and to be honest when my broadband contract finishes in 12 months I will not be renewing. 

0 Ratings
Reply