Archived

This topic is now archived and is closed to further replies.

Firon

µTorrent 1.4.2 beta 435

Recommended Posts

im having a lot of X flags even when PXE is not enabled in utorrent or the torrent, first i thought it was about having them by DHT, but then i saw a few peers that had no H flag and still had the X flag

Share this post


Link to post
Share on other sites

There is still a bug in 418.

I have disabled outgoing encryption and a remote client has "enabled always" (both 418).

Sometimes we have an E flag, sometimes not. It should always be encrypted as at the other side is forced.

The first attempt had no E, i said him to stop torrent and restart and we had an E.

It seems that if i start connection we never get encryption no matter what.

Share this post


Link to post
Share on other sites

I agree with The Mighty Buzzard.

'enabled always' means the remote client only accept encrypted connections.

And when you make a non encrypted connection to him, he won't accept it.

Share this post


Link to post
Share on other sites

Notice that Outgoing text next to the options? It controls just that, outgoing. Nothing more.

There's also an option to disable non-encrypted incoming connections. It's not possible to disable receiving encrypted connections.

Share this post


Link to post
Share on other sites

well that's good, because disabling incoming encrypted connections would litterally screw the people who have an ISP which throttles BT traffic to a standstill and what not ^_^

People who get throttled totally should uncheck the legacy connection checkbox and have Encryption always on.

People who aren't throttled should just leave the settings alone (disabled for outgoing) and make sure they can accept incoming connections.

That way people it will be as normal for the exception that throttled users should be able to download better. ^_^

now enough of my drunken ramblings ^_^ lol

Share this post


Link to post
Share on other sites

Just a note with the seed only scheduler, it is working great for me so far and even allows to me keep a torrent as downloading, but will not download anymore but still upload the pieces I have.

However can it be made that a force start on a torrent will override the scheduler and still download it?

Cheers

kulprit

Share this post


Link to post
Share on other sites

Sorry Firon, I am saying that a force start is not currently bypassing the seed only mode of the scheduler, and I was wondering if it could be made so it did.

Share this post


Link to post
Share on other sites

Oh, it's not? Hm, I must've misread what you said...

And shirokage: that's because there isn't one for beta 418 :P

Share this post


Link to post
Share on other sites

It also doesn't work perfectly yet, every once and a while 1 or 2 torrents jump up to 20k/s for a minute then drop back to zero. Does it everyone once and a while. Still a great addition to a great client.

Share this post


Link to post
Share on other sites

@alcoholjunkie wrote:

People who get throttled totally should uncheck the legacy connection checkbox and have Encryption always on.

People who aren't throttled should just leave the settings alone (disabled for outgoing) and make sure they can accept incoming connections.

My isp is shaping in en outgoing connections

So clients who disable encryption can not give me full speed or cant connect at all if i turn off legacy connections So everybody have to enable it.

Am i wright?

Grts Blimmel

Share this post


Link to post
Share on other sites

Sorry guys but i do not understand.

If i have ENABLED ALWAYS, and another 418 connects to me, we should ALWAYS have an E, even if he has disabled. Else how i can bypass my ISP?

In fact i wasn't only uploading to him but downloading too and i was limited in download from that client at 1-2KB/s by my ISP.

When i restarted the torrent then we had an E as we should.

Is it more clear?

How it is working now it's useless 50% of the time.

if by chance i connect to him first, we have an E, if he connects to me first, we do not have it, even if in the future i start downloading from him.

Share this post


Link to post
Share on other sites

domz: if i disable that, will i be able to download from standard client without encryption? it is not clear.

If the answer is yes, they should disable it automatically when setting encryption always

Share this post


Link to post
Share on other sites

I agree with skynetman, I think it should be like this:

I have PE "Enabled, Always" - if peer tries to connect me (incoming connection), connection should be encrypted even if peer has disabled outgoing PE, and my µT shouldn't allow unencrypted connections

I have PE "Enabled" - it should allow unencrypted connections from "non-µT/Azureus" clients, but still encrypt data from µTorrent and if possible Azureus

Because now it's useless if it's incoming connection and peer has PE disabled

Share this post


Link to post
Share on other sites

However, I'm not sure that it don't encrypt packets if it's incoming connection, since i've never actualy tested it, maybe i'll do some testing later

Share this post


Link to post
Share on other sites

Hello.I have the last version and this settings.....Protocol Encryption=enabled.Allow legacy incoming connections=checked and peer exchange=checked.It seems to work fine like this for me!!What do you think??But i don't know one thing....:advanced options-diskio.read_cache_size.i must leave it 0 or change it?Sorry about my english........!!!!!!

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.