Interleaving

[Wingco1]

Well it appears when it`s on it stays on. As some will know I had a prob with me old trusty speedtouch modem which caused a number of resyncs in a short space of time. This I assume resulted in Interleaving being turned on.

When I connected up my router sure enough the Path was shown as interleaved. I have a rock solid sync of 8128/448 since I was maxed so the speedtouch resyncs could be the only cause.

It would seem that if the BT gear decides to turn on interleaving that`s it. It doesn`t restest during the initial ten days to see if the line has stablised an turn it off

Anyhow an email to support resulted in a phone call from Simon. Suprisingly he thought interleaving wasn`t as bad as it`s being painted, except for gamers due to the higher pings. Well he agreed to submit a modify order to have it turned off, which happened in the early hours this morning.

With regards to pings. Up here in Cumbria it appears I am connected to the Edinburgh RAS, which is 100 miles North as the crow flies. My pings were never great usually in the 40+ms, using my speedtouch and regardless of ISP. I ran a couple of tracerts with interleaving on;

Tracing route to www.bbc.net.uk [212.58.224.89]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  mygateway [192.168.1.1]
  2    47 ms    46 ms    46 ms  uk.dsl4.idnet.net [212.69.63.37]
  3    48 ms    45 ms    47 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  4    44 ms    45 ms    46 ms  212.58.238.129
  5    47 ms    46 ms    47 ms  www.bbc.net.uk [212.58.224.89]

Trace complete.


Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  mygateway [192.168.1.1]
  2    46 ms    45 ms    46 ms  uk.dsl4.idnet.net [212.69.63.37]
  3    44 ms    48 ms    45 ms  www.idnet.net [212.69.36.10]

And the same after the switch off;

Tracing route to www.bbc.net.uk [212.58.224.118]
over a maximum of 30 hops:

  1     4 ms     1 ms   <10 ms  mygateway [192.168.1.1]
  2    28 ms    28 ms    28 ms  uk.dsl4.idnet.net [212.69.63.37]
  3    27 ms    28 ms    30 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  4    27 ms    28 ms    27 ms  212.58.238.153
  5    27 ms    29 ms    28 ms  www.bbc.net.uk [212.58.224.118]

Trace complete.

C:\>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms     1 ms   <10 ms  mygateway [192.168.1.1]
  2    27 ms    27 ms    29 ms  uk.dsl4.idnet.net [212.69.63.37]
  3    28 ms    27 ms    27 ms  www.idnet.net [212.69.36.10]

Trace complete.

Pretty conclusive I would say

[Scott]

Fascinating Wingco and very informative mate.
Thanks for taking the time to post.

[Bill]

Thanks for that mate. Looks like interleave on your line was worth about 20msec on pings, which I think is at the low end of most estimates. They must have fast kit at Edinburgh 

[Jeff]

Nice post Wingco

[TimJ]

From here in Worcestershire with interleaving on I get pings 37-40mS.

Before interleaving was turned on the line was very unstable so don't have the option to turn it off.

Pinging www.bbc.net.uk [212.58.224.82] with 32 bytes of data:

Reply from 212.58.224.82: bytes=32 time=40ms TTL=252
Reply from 212.58.224.82: bytes=32 time=37ms TTL=252
Reply from 212.58.224.82: bytes=32 time=38ms TTL=252
Reply from 212.58.224.82: bytes=32 time=37ms TTL=252

Ping statistics for 212.58.224.82:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 40ms, Average = 38ms

[Gilba]

Same here, had to have it on to stablise my line.

Here's mine with interleave turned on

Tracing route to www.bbc.net.uk [212.58.224.123]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    23 ms    24 ms  uk.dsl4.idnet.net [212.69.63.37]
  3    23 ms    23 ms    23 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  4    24 ms    25 ms    23 ms  212.58.238.153
  5    24 ms    23 ms    22 ms  www23.thdo.bbc.co.uk [212.58.224.123]

Trace complete.

Was between 12-14ms without.