![]() Registered Member ![]()
|
I played a bit with iptables and set up my simple firewall. Everything seems to work fine, exept I see in my logs blocked incoming connections on various ports when I run KTorrent or qBittorrent.
The default policy of my iptables firewall is to accept all outgoing connections and drop all incoming connections:
And then I made four exception rules for incoming traffic: 1. Open torrent listening and DHT port on 33333 :
2. Open port 1900 (UPnP) to let application forward port 33333 on my router:
3. Open port 6771 for local peer discovery:
4. I'm not sure why Ktorrent and Qbittorrent use port 5353 (mDNS) but it's open:
So everything seems ok: 1. router says port 33333 is forwarded with UPnP/NATPMP 2. both applications QBT and KT don't report errors and speeds are good However in iptables' logs I see blocked incoming tcp connections on various ports with RST flag when torrent applications are running. After some time there are rather many of them. Example:
Is everything really OK? Why they keep connecting on these ports? |
![]() Moderator ![]()
|
Those are incoming reset packets, I would guess they are from failed connection attempts. You should let these through though, that way ktorrent will know quickly if a connect failed. Otherwise you will have to wait for the 30 second connection timeout, which will slow down connecting to peers.
|
![]() Registered Member ![]()
|
Thanks for the answer. I will try to fix this problem somehow. In fact it seems my download speed is somehow affected. Solving it may be difficult because of various ports and ips of connections and the only common thing is rst flag (or ack fin/ack rst). It also surprises me than nobody mentioned about this problem anywhere because it clearly shows that forwarding/opening one port for listening/dht is not enough for torrents.
EDIT: I also forgot to write in the first post that I have allowed all incoming related and established connections:
|
Registered users: abc72656, Bing [Bot], daret, Google [Bot], lockheed, Sogou [Bot], Yahoo [Bot]