bt.transp_disposition=16 gives no in/out traffic after uT has started

[niktarace]

Hello.

I tried to set bt.transp_disposition to 16 (uTP header) but after I started uTorrent, I saw no in/outcoming connections even if I was downloading torrents with many clients uT 2.0.

I looked at the logger, and all TCP and uTP incoming connections were not allowed.

When I allow uTP outgoing connections (16+2), traffic appears but I thought 16 was the value to accept only uTP traffic...

So how is bt.transp_disposition=16 supposed to work?

Do I need to be connected to peers with the same value of bt.transp_disposition?

What's the value to accept only uTP connections (in & out)?

NB: version uT 1.8.4 16688

[DreadWingKnight]

uTP only is 10, not 16

And your current version will be unsupported within a week due to 1.8.5 being on autoupdater rollout.

[niktarace]

That's what I suspected the 1st time but what's the role of 16?

16 tells µTorrent to use the new uTP header. This is an improved communication header, but is not backwards compatible with clients that do not understand it.

And what's the difference between 10 & 16? Packet format?

[Ultima]

16 is supposed to be a cleaner header (probably less overhead and all), but isn't backwards compatible with older clients that don't understand it.

10 and 16 are not exclusive. 10 will use uTP only the old header, 10+16 = 26 will use uTP only with the new header.

[niktarace]

Ok I see the difference, there are 2 new things: uTP and uTP header.

So 16 is relative to the new uTP header, and 8+2 to uTP traffic.

I understand why I saw no traffic whith 16, because I enabled only the new header, but not the traffic (TCP and/or uTP).

Are the next versions of uT (2.0 & 2.1) with the new uTP header by default?

[Ultima]

That's the plan, yes.