I have two locations connected with wireguard, location_NAT and location_PUB.
Location_PUB has public IP, the other location_NAT is behind NAT.
I have NAS with torrent client in location_NAT, but I cannot seed/upload effectively to have decent DL/UL ratio if I don’t expose torrent TCP port.
I think I’m almost done this.
I’m able to test this solution with SSH deamon on NAS in location_NAT. I can connect from Internet to NAS SSHD (location_NAT) via location_PUB ISP.
/routing rule add action=lookup-only-in-table disabled=no src-address=NAS_IP/32 table=location_PUB
/ip firewall nat add action=dst-nat chain=dstnat dst-port=22 in-interface-list=WAN protocol=tcp to-addresses=NAS_IP
but when I dst-nat torrent port (to same NAS), then telnet connection works, but it doesn’t make me “active”, torrent tracker says “not active”.
Looks like torrent needs to use NAT to talk on different dynamic ports, but it can only talk with one torrent_port.