Fast Path on Connect

[IWasNotTheEnemy]

did you read what i asked also - if you're not syncing @ 8Mbps already then BT will tend to ignore requests for the line change...

[googleme]

Did not notice that

[gdeagle]

How do I tell what speed I am syncing at? I'm at work at the moment, is the sync speed the up/down speed that the router displays, rather than the speed shown on a speed test?

[gdeagle]

Ok, my stats are as follows
up down
connection speed: 7616. 448
Attenuation: 28db 16db
Noise Margin: 15.4db 24db

do those stats seem ok for fastpath?

[IWasNotTheEnemy]

id say so yes - tbh there's more to be had on the line...are you in your master socket?

[gdeagle]

I don't actually have a master socket, I've checked before, I only have 1 socket which I have taken the face off but there is no other socket.
I have also tried to remove my bell wire but there was only 2 wires connected to the socket so i left it alone!
We live in a fairly old house.

edit: sorry got confused with test socket! I am in the master socket, I don't have a test socket

[Undecided Adrian]

Trouble is that BT also traffic shape and you also may be experiencing that when you slip into peak hours as it seems a bit odd that you only experience it during the evening.

It could also mean that the whole BT network is just suffering from all the school kids getting home.

I noticed when they went back to school that the internet got a lot better during the day.

[gdeagle]

I know they shape heavy traffic, and I don't really mind having my speed throttled, if I am downloading something large I do it overnight.

Gaming is only tiny packets therefore should not need to be shaped and pings of over 200 are surely not acceptable.

[Craig8718]

Silly question here but can someone explain the whole Fast path thing to me? I probably use my net 70% of the time for playing PS3 online. I'm on the connect package and I reckon it is quicker on my PS3 (not so much for lapyop mind) then when I was on the Mid package at my previous address.

[gdeagle]

Interleaved is a protocol which jumbles up the data and re-assembles it at the other end.
This is to protect the data against burst errors which can overwrite sections of the code.

a basic example.
CODE= Turn Left Now

If there is error during transmission, the code could look like this

CODE= Turn __t Now
This data is hard to correct as nearly all of an instruction is missing.

Interleaving jumbles up the code like so
CODE= NrLf ueow Tnu

Now if you have the same error you would get this
CODE= NrLf ___w Tnu

When the data is re-assembled you get
CODE= T_rn L_ft N_w
This data is easier is much easier to correct as the instructions are only partially missing

Fastpath is much faster as it just sends the data as soon as it is received and can send it in bits like
Turn
Left
Now

Interleaved has to wait for the whole instruction before it can jumble it up then send it.

That was a-lot more long winded that it was supposed to be, sorry!