amonrei Posted February 4, 2006 Report Share Posted February 4, 2006 418 seems to work fine now with PE enabled. Link to comment Share on other sites More sharing options...
Blimmel Posted February 4, 2006 Report Share Posted February 4, 2006 418 version works fine with peConnecting is ok alsoGrts Blimmel Link to comment Share on other sites More sharing options...
hofshi Posted February 4, 2006 Report Share Posted February 4, 2006 418 solved the "only remote connections" for me. Link to comment Share on other sites More sharing options...
Nefarious Posted February 4, 2006 Report Share Posted February 4, 2006 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 Link to comment Share on other sites More sharing options...
alcaholjunkie Posted February 4, 2006 Report Share Posted February 4, 2006 Nefarious: Were them peers Incoming too? maybe they connected to you via PEX? Link to comment Share on other sites More sharing options...
boo Posted February 4, 2006 Report Share Posted February 4, 2006 the PEX possibly needs to be more worked on to work correctly. Link to comment Share on other sites More sharing options...
skynetman Posted February 4, 2006 Report Share Posted February 4, 2006 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. Link to comment Share on other sites More sharing options...
The Mighty Buzzard Posted February 5, 2006 Report Share Posted February 5, 2006 Yeah, that's how it's supposed to work. You told yours to never try to make encrypted connections so it isn't trying. He told his to only try to make encrypted connections so his does. What'd you expect? Link to comment Share on other sites More sharing options...
boo Posted February 5, 2006 Report Share Posted February 5, 2006 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. Link to comment Share on other sites More sharing options...
Firon Posted February 5, 2006 Author Report Share Posted February 5, 2006 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. Link to comment Share on other sites More sharing options...
alcaholjunkie Posted February 5, 2006 Report Share Posted February 5, 2006 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 Link to comment Share on other sites More sharing options...
kulprit Posted February 5, 2006 Report Share Posted February 5, 2006 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?Cheerskulprit Link to comment Share on other sites More sharing options...
Firon Posted February 5, 2006 Author Report Share Posted February 5, 2006 No, 'cause that's the point of force start, to bypass basically everything else. Link to comment Share on other sites More sharing options...
kulprit Posted February 5, 2006 Report Share Posted February 5, 2006 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. Link to comment Share on other sites More sharing options...
Shirokage Posted February 5, 2006 Report Share Posted February 5, 2006 Firon, The language pack also points to an invalid location at the download page. Link to comment Share on other sites More sharing options...
Firon Posted February 5, 2006 Author Report Share Posted February 5, 2006 Oh, it's not? Hm, I must've misread what you said...And shirokage: that's because there isn't one for beta 418 Link to comment Share on other sites More sharing options...
kulprit Posted February 5, 2006 Report Share Posted February 5, 2006 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. Link to comment Share on other sites More sharing options...
Blimmel Posted February 5, 2006 Report Share Posted February 5, 2006 @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 connectionsSo 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 Link to comment Share on other sites More sharing options...
skynetman Posted February 5, 2006 Report Share Posted February 5, 2006 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. Link to comment Share on other sites More sharing options...
DomZ Posted February 5, 2006 Report Share Posted February 5, 2006 You need to disable legacy "allow incoming legacy connections" for full encrypted connections. Link to comment Share on other sites More sharing options...
skynetman Posted February 5, 2006 Report Share Posted February 5, 2006 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 Link to comment Share on other sites More sharing options...
Stone Posted February 5, 2006 Report Share Posted February 5, 2006 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 connectionsI have PE "Enabled" - it should allow unencrypted connections from "non-µT/Azureus" clients, but still encrypt data from µTorrent and if possible AzureusBecause now it's useless if it's incoming connection and peer has PE disabled Link to comment Share on other sites More sharing options...
skynetman Posted February 5, 2006 Report Share Posted February 5, 2006 exactly. So u can remove "allow legacy" option and change "encryption, always" to "encryption always, when possible" to make it more clear. Link to comment Share on other sites More sharing options...
Stone Posted February 5, 2006 Report Share Posted February 5, 2006 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 Link to comment Share on other sites More sharing options...
Abigail Posted February 5, 2006 Report Share Posted February 5, 2006 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........!!!!!! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.