Transmission

Either the EditConfigFiles wiki page has recently been updated, of I have overlooked the fact, that max-peers-global is a legacy option from 1.4x, which has been replaced by peer-limit-global. I guess I can delete that option from my settings.json. Then it makes sense, to just have to adapt * peer-l...

That OT, but it's definitely not a problem due to shitty ADSL router here, because my ADSL modem is used in bridge mode, PPPoE is done by my firewall-gateway, and I'm still using transmission with the default settings (so "max-connections"=200). Since my guess is "max-peers-global&quo...

Just updated to v.1.51 recently, but this behavior still exists. I was always using the blocklist function, but these bogon-connection-attempts are still popping up: Chain valid-dst (2 references) pkts bytes target prot opt in out source destination 51 2832 REJECT all -- any any anywhere 2.0.0.0/8 r...

Since I am actually investigating strange connection drops from my ISP, I was wondering if it is about too many open connections on my transmission-daemon v.1.51 machine. Looking through settings.json, I only can find "max-peers-global": 200, "peer-limit-global": 240, "peer-...

I also just wondered, how this setting can be handled. If anybody knows what to to with peer-socket-tos, please share your knowledge.

My firewall-gateway first filters all incoming and then outgoing packets from/to the internet according a well known bogon list . The awkward thing is now, that only very few packets try to come in from such a prohibited network, but quite some try to go out to such a bogon network from Transmission...