it seems like i always get snubbed by the peers
no matter how many peers connected
i always have 60-80 of peers snubbed shows YES

how snubbed works?

why am i being snubbed?

what is the reason that may cause this?

snubbed "yes" has causes me to lose connected peers and eventually no peers connected.

i dont have NAT problem or DHT problem as azureus works well with me

ktorrent since version 2.0.1 till the current latest svn source i have this problem which causes me to have very slow downloads as in < 20kbps and usually between 0-5kbps

i have a feeling that other client just refused to send package to ktorrent.

Being snubbed means that you haven't received a piece from a client in the last 60 seconds. It happens for a lots of reasons. For example, if you are choked by a client for 60 secs your 'snubbed' column will show 'yes' - this is the most common one. You can also be snubbed for some uncommon reasons like older versions of BitComet which granted an upload slot but just don't send anything, or some other reasons.

But, we seem to have an issue with somewhat lower download speeds and we are working on it.

so is it normal for ktorrent to drop the connection to peer after certain time being flag as snubbed?

my ktorrent client is dropping peers who flagged snubbed after a period of time.

y not it maintain the flag snubbed peer and retry to request later and unmark the snubbed flag if peers not choking me.

laiseng wrote:so is it normal for ktorrent to drop the connection to peer after certain time being flag as snubbed?

my ktorrent client is dropping peers who flagged snubbed after a period of time.

Pretty normal i think yes. Every client is trying to replace the connections with (possibly) better performing peers in an interval. So if you're not getting anything back in a while, the chances are high a peer gets kicked from your peer list.

y not it maintain the flag snubbed peer and retry to request later and unmark the snubbed flag if peers not choking me.

Choking is not triggered because of being snubbed by the other side, or at least not directly. Maintaining every connection would be only usefull if there are not other possible better sources in swarm. I think that's pretty much what KTorrent does.

i'm downloading this torrent that have over 3000 leech and 1900 seeders

at first it started with connected 20 peers and then after 3minutes or so it drop to 10 and then after 15 minutes still 10 occationally 11 12 basically
it maintain 10-12 peers

the longer i wait the fewer peers it gets

ktorrent should keep on try to connect to all the available peers like what azureus or utorrent does

i've load this same torrent to utorrent using wine and done the same with azureus and within 10 minutes i'm getting more than 100 connected peers

and atleast 10 of those peers are sending some packages to me.

the same torrent on ktorrent shows different behaviour...

i've set ktorrent to accept 500 connection per torrent and max connection to 1000.

there certainly something wrong with the algorithm of ktorrent on connecting to peers and requesting for packages from peers.

as i type now it current drop to 8 peers now..

no sign of ktorrent trying to connected to any available peers

and i've run ktorrent in --debug mode and notice that there is alot of authentication failed message from debug mode

is that normal?

Code: Select all

ktorrent-16-09-06
encryption on
allow unencrypted connection
DHT on with 91 nodes

[/code]

laiseng wrote:i'm downloading this torrent that have over 3000 leech and 1900 seeders

at first it started with connected 20 peers and then after 3minutes or so it drop to 10 and then after 15 minutes still 10 occationally 11 12 basically
it maintain 10-12 peers

the longer i wait the fewer peers it gets

Assuming the scrape data it correct i think we can call this a problem yes.

ktorrent should keep on try to connect to all the available peers like what azureus or utorrent does

I think we first need to know what is causing this.

i've load this same torrent to utorrent using wine and done the same with azureus and within 10 minutes i'm getting more than 100 connected peers

and atleast 10 of those peers are sending some packages to me.

the same torrent on ktorrent shows different behaviour...

i've set ktorrent to accept 500 connection per torrent and max connection to 1000.

there certainly something wrong with the algorithm of ktorrent on connecting to peers and requesting for packages from peers.

as i type now it current drop to 8 peers now..

no sign of ktorrent trying to connected to any available peers

So it actively drops out, hmm, that's weird. I know KTorrent somewhat always seems to lose a connection with Advanced CTorrent, but more than that i have seen it functioning pretty well here. We need get the same circumstances and try reproducing what is causing this, it's quit extreme.

and i've run ktorrent in --debug mode and notice that there is alot of authentication failed message from debug mode

That is some information to go from, maybe we're doing something too strict? Hmm, it's normal in KTorrent yes, but it shouldn't get "out of controll", as it probably does here.

may i know does ISP throttling on p2p may affect the drop out rate like what i'm having currently?

how can ISP throttle torrent packages when i've put ktorrent into encryption mode and allows non encryption mode to connect?

My ISP seems to throttle the p2p bandwidth but i dont have hard evidence to be sure of that.

laiseng wrote:may i know does ISP throttling on p2p may affect the drop out rate like what i'm having currently?

Probably not if the ISP's aren't able to force limits on how many connections you can use on one port. But i have to admit i don't know whether they are able doing that or not.

how can ISP throttle torrent packages when i've put ktorrent into encryption mode and allows non encryption mode to connect?

Good question. They can either limit or dump connections, or limit the bandwidth, but nothing more i guess. Bandwidth limiting is already reality today on some ISP's, but the limiting of connections not yet i think. But who knows what they come up with next, those routers are pretty advanced nowadays.

My ISP seems to throttle the p2p bandwidth but i dont have hard evidence to be sure of that.

Well, if they did that and if that would be the problem when using KTorrent, you would have the same problems with other clients. At least, that's my thought my this seat.

laiseng wrote:may i know does ISP throttling on p2p may affect the drop out rate like what i'm having currently?

Well, euhm, that would be rather insidious. I haven't heard about behavior like this though.

how can ISP throttle torrent packages when i've put ktorrent into encryption mode and allows non encryption mode to connect?

If you allow non encrypted connections, they can still throttle those.

My ISP seems to throttle the p2p bandwidth but i dont have hard evidence to be sure of that.

If you see significant speed increases when you only allow encrypted connections, then it is safe to say that your ISP is throttling.

may i know does ISP throttling on p2p may affect the drop out rate like what i'm having currently?????


_________________
NOOR

laiseng wrote:may i know does ISP throttling on p2p may affect the drop out rate like what i'm having currently?
www.kitchenlola.com
how can ISP throttle torrent packages when i've put ktorrent into encryption mode and allows non encryption mode to connect?
discover on this blog
My ISP seems to throttle the p2p bandwidth but i dont have hard evidence to be sure of that.

The drop out rate on my ktorrent reduced significantly when I started encrypting all my connections with a VPN. You don't need hard evidence to prove your ISP is throttling bandwidth most do it and don't even inform users. I would recommend you start using a VPN and see the results.