This is two requests pertaining to Ktorrent's transport overhead usage

1) Show the UL/DL torrent transport overhead usage alongside the net torrent transport network usage at the bottom of the window

2) Add a network setting to allow the rate limit to included transport overhead (TCP/UDP)


This is a very, very important request to help me manage my network rate limits (as dictated by my ISP).

wlbrenne wrote:This is two requests pertaining to Ktorrent's transport overhead usage

1) Show the UL/DL torrent transport overhead usage alongside the net torrent transport network usage at the bottom of the window

All speeds shown include bittorrent protocol overhead

2) Add a network setting to allow the rate limit to included transport overhead (TCP/UDP)

TCP packets are made inside the kernel, further more the kernel decides when to send, how big the packets are, and when to retransmit lost packets. You can only get at this information from userspace by sniffing the network interface. Which is totally impractical to do.

This is a very, very important request to help me manage my network rate limits (as dictated by my ISP).

I suggest you take a look at HTB queuing (http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm), it is the right way to do this kind of thing.

I think misused the term "transport". (That's the last time use a uTorrent term without thinking of its other usage). I didn't intend to refer to the Transport Layer (http://en.wikipedia.org/wiki/Transport_layer) or Internet Layer (http://en.wikipedia.org/wiki/Internet_Layer), or the overhead in those layers.

I'm referring to the overhead that ktorrent/libktorrent has to do in initiating and maintaining communication with the trackers, DHT nodes, seeds, peers, etc. Or another way of stating it, I'm referring to "overhead" as being the network communication that ktorrent/libktorrent sends and receives that isn't directly pertaining to transferring of file chunks. I hope that's more clear.

I'm not sure to what term to refer to it as other than overhead, communication "bookkeeping"?

All speeds shown include bittorrent protocol overhead

But if the UL/DL speeds shown and UL/DL rate limits already includes the "overhead" that I'm referring to, then great, ktorrent is already doing what I want it to do.

They don't include µTP overhead, DHT traffic, tracker announces and scrapes.