[µTorrent 1.4.2 beta 435]

Using 425 here, I am trying out the new 'category list' feature.

I noticed that a torrent that completed didn't automatically move itself to the 'seeding' category while 'downloading' category was on-screen, I had to re-select 'downloading' to make it go away.

This is a minor quibble, but should be corrected one day.

[µTorrent 1.4.2 beta 435]

Sure, but the example I was giving, of the 10 Az clients connected 6 had E, and 4 didn't.. and none of them had H or X flags.. straight tracker connects.. that's why I wondered.

Oh well it's fun, only problem today is that I have nothing I want to download. Feeling withdrawal.

[µTorrent 1.4.2 beta 435]

It bears clarification here that if you make an outgoing connection and have E on, then E will be activated.. but if the remote user doesn't have E on, and connects to you, and you have allow legacy on, then there will not be an E.

In case anyone wondered why there is a mix of on and off. I leave mine on E and allow legacy because my port isn't throttled yet in this area, and to help out the folks who are.

I wonder if I had disallow legacy on, would the remote end re-negotiate to include the E.

[µTorrent 1.4.2 beta 435]

With 422 more people show up with the E flag than before.

My messed up torrent also managed to complete too (but who knows if that was because I turned on pre-allocate in a vain attempt to solve mystery).

[µTorrent 1.4.2 beta 435]

In the torrent I'm running right now I see 2 Azureus 2400s and they both have E's and I see 4 µTorrent 1.41B's but only ONE has the E flag.

[µTorrent 1.4.2 beta 435]

Bug report from another message:

"Eek, I just turned verbose on in the log and then unchecked it but it's still scrolling away madly. Definitely a bug there.

Interesting.. seeing Disconnect: no such torrent go by here and there in the log."

and

"But how about this though.. in the logging at :00 it banned an IP and then 30 seconds later it banned the exact same IP again twice.. If an IP is banned, then logically it should be for longer than 30 seconds right?

Hmm it did it again, banned a different IP and then 6 minutes 25 seconds later banned the ip again?"

[µTorrent 1.4.2 beta 435]

If folks need a big Torrent with a ton of encryption compatible clients on it to test out: http://torrents.aelitis.com:88/torrents/Azureus2307-B46.jar.torrent

It's about 6 megs and has hundreds of 2307 clients on it. So you could uncheck legacy compatible and try the E flags if you wanted to.

[µTorrent 1.4.2 beta 435]

Actually no Firon.. I'm still able to dl at near 300 k/s on a populated torrent and my u/l is unaffected, and this is with unencrypted clients.

So if they're stopping 1720, it must be on a per client or per geographic region basis, and mine hasn't been reached yet.

[µTorrent 1.4.2 beta 435]

Earlier today I was connected to a beta 1.41 user on Rogers, and the user was uploading at 40k/s to me.. This is with an E flag turned on.

I don't know which port the user was on (i.e. were we both on 1720) but it's a good sign!

[µTorrent 1.4.2 beta 435]

I'm using the 418 build, and I must say I find it annoying meeting a µTorrent 141B client in the peers list, getting an E flag usually in combination with H and/or X and that client does not want to send or receive anything to me.

Maybe it's because they don't know how to configure their firewall or something.. but the nonencrypted ones work fine..

Won't know for sure what the problem is until more people start using it.