Transmission

And that would be the X-Forwarded-For header. The Transmission Port Check server is configured incorrectly for cases where a proxy is in a private subnet and adds a X-Forwarded-For header. The port check server should check if the X-Forwarded-For http header is a private address and if it is it shou...

Just FYI, if you're having trouble getting a peer listening port open and you have a WebProxy... -I'm running NAT on a MicroTik RB450G with port forwarding correctly configured. -Transmission reports that the specified listening port is CLOSED - http://www.whatsmyip.org/port-scanner/ reports that it...

I think the justification for separate bandwidth controls is pretty simple and strong. If there were no problems with ISPs and no problems with saturating uplinks we would all run our clients without bandwidth controls at all, contributing as much to the swarm as possible. On the local network the s...

It would also be nice to have a menu option to "Discover Local Peers" (as in schedule a local peer announce for now). Sometimes it seems like the normal discovery takes ages, even when only a single torrent is running.

Think of it as the local compliment to "Update Tracker".

Note that Ignoring bandwidth limits would work both ways, so a peer that is choked to the internet should appear unchoked to local peers. Some designation that a peer is local in the inspector would be nice, maybe something superimposed on the encryption icon. Also LPD should be on by default. I can...

Now that we have Local Peer Discovery we need a few options: Stay Connected to Local Peers Local Peers Ignore Connection Limit (Or Prefer Local Peers) Local Peers Ignore Bandwidth Limits [/color]I think that Local Peers Ignore Bandwidth Limits is the most practical but I can see usefulness in a myri...