Mikrotik: portmapping on the external interface and the client from the local network cannot connect using the white address of the router. Is there a solution?

Question

Mikrotik

Hello!
There is the following configuration: a Mikrotik router (RouterOS 6.18), PPoE Internet (external address 69.69.69.69), several computers in the local network. On one of the comp-ditch (192.168.0.2) a certain service listens to tcp port 128, in connection with which a port was forwarded from the outside for external clients:
add action=dst-nat chain=dstnat dst-address=69.69.69.69 dst-port =128 protocol=tcp to-addresses=192.168.0.2 to-ports=128
Everything works as expected.
Then there is a need for a client from the local network to connect to the service, using as a target not the local address 192.168.0.2, but the external 69.69.69.69; after which it turns out that for local clients only pinging the external address of the router is successful, and attempts to connect to any of the known open ports (22, 80, 128) are unsuccessful.
Because I didn’t come across Mikrotiks before, then, apparently, I either missed something in the documentation, or I just don’t understand.
There are no tricky firewall\nat\routing rules, local clients have no restrictions or problems accessing the Internet.
Also, a similar configuration (accessing the router from the local network using an external address) worked on budget routers (like a dlink-asus) without additional routing or firewall rules.
Attempts to write any duplicate rules for this particular non-local address (after all, access and masquerading from the local network to the external one are already allowed and working) did not lead to success.
Actually, the question itself is: what should Mikrotik do so that the client 192.168.0.1 can successfully connect to 69.69.69.69:128 ? Or is it an incorrigible feature of Mikrotik?

Answer 1

wiki.mikrotik.com/wiki/Hairpin_NAT

Answer 2

Most likely - a feature of Mikrotik.
There was a similar task - on Mikrotik on the external interface there are several external white addresses, several subnets are made behind NAT, on different internal ports. Forwarded RDP port from one external address to internal 192,168,24,18. It works outside, from its network 192.168.22.XXX - does not work. No decision was made within a reasonable amount of time.

Answer 3

dumb question. what for?)