1.8.3 with uTP can't bypass my ISP's TS, but 1.9 can!

[mw1001]

Hi,

For the last few months I was running 1.8.3 betas with uTP on, with extreme success to bypass my ISP's traffic shaping.

But, for the last 15 days, 1.8.3 can't bypass TS anymore, but 1.9 still able to do it.

The problem: some private trackers, like pretome, doesn't allow 1.9 yet, because this is a beta build (well, so is the 1.8.3, but this one is allowed).

Why in one build the uTP is working to bypass TS, but in the other not? Is there so much difference to this is happen, or the is some problem with the last (or two last) 1.8.3?

Regards.

[Switeck]

Slight differences in uTP connections maybe?

Even packet size may be different.

Have you disabled "allow legacy connections" and set outgoing encryption to FORCED?

[mw1001]

In both versions, the settings is the same.

Encryption is "forced", but "allow legacy connections" is checked.

The strange question is why 1.8.3 used to bypass TS from my ISP and now isn't able anymore? Quiet odd...

Regards.

[Switeck]

Their DPI hardware may have had a recent update that spots uTorrent UDP traffic based on the smaller packet sizes that v1.8.3 uses.

Chances are they don't care much if they block other things on accident.

[mw1001]

I'm pretty sure they are aim on torrents.

At weekends they turn off TS late at night (dawn, around 2am ~ 7am). When TS is off, I can get 10mpbs with TCP (bt.transp_disposition = 5) and around 6~7mbps with uTP (bt.transp_disposition=15).

Regards.

EDIT!!!

Right now I updated the 1.8.3 to build 15571.

Now with uTP is bypassing the TS from my ISP, just like 1.9!! Not fast as TCP when TS is off, but MUCH better then TCP when TS is on!

Whatever was wrong with previous version, is now fixed!

Regards.