check firewall
Based on the MT docs I tried this: SRC is IP of MT router, DST is IP of my NAS
Beside this... both are in the same VLAN and I do not expect any firewall relevance between them.
how about 127.0.0.1?
I'm definitly not a pro with this stuff, but I thought
127.0.0.1 = localhost = myself = MT router = 192.168.10.1?
-> no FW needed if I "speak" with myself or any IP inside the same VLAN.
Anyway, I tried it with 127.0.0.1 as SRC in the 3 FW rules. still not working and FW package counter = zero.
Or did you mean something else? What kind of FW rule you do have in mind? Happy to try everything needed 
i mean router must connect to itself. try disabling all firewall rules, and then go from there
Probably rule is missing or is disabled (it is not just for CAPsMAN as defconf comment states):
/ip/firewall/filter add chain=input action=accept src-address=127.0.0.1 dst-address=127.0.0.1 in-interface=lo comment="defconf: accept to local loopback (for CAPsMAN)"
Thank you. With this rule I have now traffic on the package counter.
But anyway the rsync doesn't work - no progress so far --> still "making control connection to 127.0.0.1"
In the log I see now "denied winbox/dude connect from 127.0.0.1"
Disableing all FW rules is not an approach I'd like to follow. The FW has a reason, it's not "just a game" and I don't want to have a freeflow in my network - even not for 10 min. I'm sure we will find a sharp and fixning solution for this
I do not understand, why a solution is so complex with RSYNC? Should be so easy! Let's try now to strip down/simplify the RSYNC:
- just RSYNC a file to a folder on MT
- no SMB, no USB
- Why 127.0.0.1? Would it not make sense to use the own IP to avoid any FW issues?
But again, it doesn't work. What has to be done to make it run? FW? ipsec? soemthing else?
The MT docs says: " Port TCP/8291 is used for the control connection (if not open in the status (file sync print) you will be stuck at making control connection to YOUR_IP)"
Hence, it is maybe FW, but I opened TCP/8291 already and should it be always open between 192.168.10.1 and 192.168.10.1 = between myself?
Tried it with 127.0.0.1 instead of 192.168.10.1 as well - with no success
If this works, it will be probably easy to change it for the original question with SMB and USB
UPDATE: just added this FW rule (with counted packages)
and get now
what could be the next to avoid this new error?
Hej folks,
MTs docs says "RSYNC...or within the same system."
Is there anyone with a running example for RSYNC within the same system? Just File to another folder - to keep it as simple as possible.
If this is running, we add SMB as remote path - to come back to the original question
Appreciate any help to get this run
UPDATE 04.03.2026
bump... 
Can't believe that I'm the only one trying to use RSYNC on the same system... how to solve this ipsec issue? Any hint would be really appreciated...