Problems with IPlayer & Unlimited

[#1]

look back at my first post i think an look for the value that circled in red on an incoming packet
edit
you dont need to save the captures wen your not sumiting them to pn just view them why there running or wen you stop them

[#2]

Ok, it's 0x60.

[#3]

I have no idea what I'm doing but I followed the instructions that you gave me... 
Edit: Is that any help?

[#4]

Quote from: Oldjim

The only thing I can think is that at peak demand times the BBC offloads the stream to Akamai or similar and Plusnet categorize it as 0x06 and it all goes to pot.

No - it's not only that. I was suffering as well. I'm on the IPSC connect trial so coming in over 21CN and I'm on PAYG so everything is Gold or better (I've checked the wireshark trace and it is still 0x80 even when it is stuttering).
I'm beginning to wonder if it is a lack of peering bandwidth between Plusnet and BBC/Akami.

[#5]

Hi guys,
I had problems with iPlayer earlier too, though it seems ok now, anyone still having trouble?
We've had to do some load balancing today to try to get the network balanced again, going onto one of the under-subscribed pipes may well improve matters.

[#6]

Mand,
That doesn't explain the issue those on 21CN are seeing. Is there a shortage of bandwidth on there again?

[#7]

yeah  jameseh will point this thread out to dave most likely tomoz afaird there nothing that can be done tonight luckly your on unlimited so i would think that the workaround that was able to be used on my unlimited account would be used on yours to if this is same problem i had a month ago.
with oldjim effected to tho iam on the thinking bbc have increased there ip range to cope with the tennis and PN taffic mangment sig is not set up for these ips but lets see wat dave says tomoz

[#8]

I don't think the signature will be working on (just) the IP. It wouldn't surprise me if the same Akami IP is serving other download traffic which should be 0x60.

[#9]

Quote from: ASBO

yeah  jameseh will point this thread out to dave most likely tomoz afaird there nothing that can be done tonight luckly your on unlimited so i would think that the workaround that was able to be used on my unlimited account would be used on yours to if this is same problem i had a month ago.

No problem it's getting late anyway. I'll check back tomorrow! Thanks for your help! 

[#10]

sry MAND but iam thinking that load balncing would not effect iplayer streaming sig

[#11]

The sig we have should work regardless of IP address and port that iPlayer uses. We're still working with our suppliers to develop a better signature for iPlayer, if you've got captures then please let me have them. We do have a problem on 2 of the gateways (not 21CN) where the signature for some reason isn't working properly, we have a separate case open with the suppliers to try and find out why. So if you can also post which gateway you see 0x60 on that would be appreciated.
Jelv, don't suppose you tried (or if it happens again can try) on RIN? Also could you post a tracert to the server that's serving the stream? Would be useful to see what route it takes out of the network. There's plenty of spare bandwidth on IPSC (we have 21Mbps of bandwidth and peaked at 3Mbps this evening). I think we peer with Akamai over LoNAP and have at least one 10Gbps link so not sure if it's capacity related on the peering but there could be a different route being taken or somewhere further upstream.

[#12]

Trying to watch Wimbledon highlights at the moment and it's awful!
I've never seen the NetMeter graph look like this before when trying to stream!

C:\Documents and Settings\John>tracert 86.53.218.13
Tracing route to host13.akamai-thn.cust.telecomplete.net [86.53.218.13]
over a maximum of 30 hops:
  1     1 ms    <1 ms    <1 ms  dg834 [192.168.0.1]
  2    14 ms    15 ms    14 ms  lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
  3    14 ms    13 ms    13 ms  vl604.thn-gw2.plus.net [84.92.4.170]
  4   172 ms   227 ms   233 ms  vl23.pte-gw2.plus.net [212.159.4.28]
  5    15 ms    15 ms    17 ms  linx1.telecomplete.net [195.66.224.139]
  6    14 ms    16 ms    15 ms  host13.akamai-thn.cust.telecomplete.net [86.53.218.13]
Trace complete.

[#13]

RIN is looking better but it also shows the same peaking pattern on NetMeter - I'm wondering if that is the difference between watching the current program on a channel and a previous program...
Just tried watching current BBC 2 and that is the case.
I'm also seeing stuttering on RIN which is coming from a different server:

C:\Documents and Settings\John>tracert 92.122.127.140
Tracing route to a92-122-127-140.deploy.akamaitechnologies.com [92.122.127.140]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  dg834 [192.168.0.1]
  2    11 ms    12 ms    11 ms  217.47.89.122
  3    22 ms    11 ms    18 ms  217.47.89.161
  4    16 ms    16 ms    14 ms  217.47.46.174
  5    14 ms    13 ms    13 ms  217.41.171.29
  6    11 ms    10 ms    10 ms  217.41.171.78
  7    24 ms    22 ms    20 ms  217.41.217.46
  8    14 ms    11 ms    10 ms  217.47.159.82
  9    13 ms    12 ms    13 ms  core1-pos3-2.kingston.ukcore.bt.net [62.6.40.113]
 10    12 ms    21 ms    17 ms  62.172.103.98
 11    12 ms    13 ms    12 ms  core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.65.122]
 12    19 ms    11 ms    14 ms  195.66.226.168
 13    12 ms    12 ms    12 ms  a92-122-127-140.deploy.akamaitechnologies.com [92.122.127.140]
Trace complete.

Out of interest I tried a trace to the server IPSC was using while I was on RIN - the route is a bit different:

C:\Documents and Settings\John>tracert 86.53.218.13
Tracing route to host13.akamai-thn.cust.telecomplete.net [86.53.218.13]
over a maximum of 30 hops:
  1     1 ms     1 ms    <1 ms  dg834 [192.168.0.1]
  2    13 ms    12 ms    12 ms  217.47.89.122
  3    13 ms    13 ms    14 ms  217.47.88.161
  4    12 ms    14 ms    13 ms  217.47.46.170
  5    10 ms    10 ms    10 ms  217.41.171.25
  6    18 ms    17 ms    15 ms  217.41.171.66
  7    16 ms    15 ms    16 ms  217.41.171.78
  8    15 ms    16 ms    16 ms  217.41.171.62
  9    16 ms    15 ms    17 ms  217.47.46.106
 10    10 ms    10 ms    10 ms  194.72.3.113
 11    12 ms    12 ms    12 ms  core1-pos0-8-0-1.ilford.ukcore.bt.net [62.6.201.113]
 12    13 ms    12 ms    11 ms  core1-pos9-0.telehouse.ukcore.bt.net [62.6.201.118]
 13    16 ms    15 ms    15 ms  linx2.telecomplete.net [195.66.226.139]
 14    16 ms    16 ms    16 ms  v101-r2.thn.telecomplete.net [213.160.96.112]
 15    88 ms    90 ms    91 ms  gig-1-3-r5.thn.telecomplete.net [193.0.255.17]
 16   113 ms   115 ms   116 ms  host13.akamai-thn.cust.telecomplete.net [86.53.218.13]

[#14]

Quote from: dave

So if you can also post which gateway you see 0x60 on that would be appreciated.

Sorry Dave, it isn't clear to me whether you are asking me to do this or ASBO DOG or Jelv? 

[#15]

Hi there Jameseh
Any chance of getting the iplayer workaround that ASBO DOG was talking about?
(My kids have done all the gardening, promise!) 
Cheers
BlueRhizome