I certainly hope you are intending to use the bittorrent protocol for seeding Linux ISOs, or other content which is permitted to be torrented and not any copyrighted material.
You dont need the to port rules in your DST NAT rules if the dst port entered is the same.
For the firewall your need a single rule for the forward chain
add action=accept chain=forward connection-nat-state=dstnat
Thanks Sebastia and Anav, but again, I’m not super-technical & knowledgeable… could you please tell me exactly what I gotta do in addition to what I already did?
I really can’t begin to tell you what a bad idea that is.
So you’re downloading P2P, maybe one of the files is infected, this then generates multiple services on the host, all of which then tell your router to open up ports which it does because UPnP is on which then enables more malicious software and activity onto your LAN.
Please do take the time to understand dst-nat and do the job properly as UPnP really is not a lasting solution you should consider.
Concur, turn UPNP off.
Simply create the necessary DST rules as you have done, for the most part they seem fine.
For filter rule as I stated in my above post create a rule allowing those connections.
As to what Steve intimated, I would put your torrent server on its own VLAN with no access to your LAN.
I would have a pc attached to the server and get any files over to your lan by air gap if you wanted them on a LAN, after perusing them with a good virus checker.
Awesome and as noted on the NAT rules, For destination NAT if the too port is the same as the destination port in the rule (no translation required), only the destination port need be entered.
There is no harm in entering it twice and its also clear to any reader.