Transmission

You should limit your total upload in Transmission to less than your total available bandwidth.

Since BT clients in general use lots of TCP connections, virtually nothin else gets anything from the available bandwidth, so lots of BT tcp uploads which are not speed limited to less than the available ...

In the Peers list in the Inspector window the column for IP address is way too narrow for IPv6 addresses.

Please increase the max width of this column to thrize the current max or don't max it for anyone who
wishes to have lots of empty space or uses different system fonts (accessability).

Jor

I second this proposal.

However, peers without much data should not be discriminated, so i have following additions to this suggestion:

- don't modulate upload to peers that have less than $USERADJUSTABLE Percentage of data, regardless if they choke us.
- prefer upload to peers who are not chocked ...

[Edit:] apparently i was wrong. The code in peer-mgr.c does not cause the error, although it should use ntoh-macros.

I guess there are more than one host-byte-order/network-byte-order issues buried in the transmission source code.

See the other thread about this problem (net unreachable):
http://forum.transmissionbt.com/viewtopic.php?f=2&t=6758

The error-text indicates that you are not using the Mac OS X version but Linux, right?
Darwin kernel refuses the connects to Multicast IPs with "protocol not supported" (EPROTOTYPE in ...

I've seen the same Errors in my log (Transmission 1.40, haven't upgraded yet).

The reason why those connects fail ist: any IPv4 address with the first byte between 224 and 240 is a Multicast Address.
A TCP unicast client simply cannot connect to such a bogus IP address.

I do not know why ...