NAT without proper GW what's logic

https://drive.google.com/file/d/0B1Pbe3Mxo264VUFPX1FlTGlqSFE/view?usp=sharing
Hi everyone! My topology is pretty simple.
I need to access web server (192.168.88.12) from outside ip address 10.7.8.141. GW of WebServer is not mikrotik interface.
And it’s works with

1    chain=srcnat action=masquerade protocol=tcp dst-address=192.168.88.12 out-interface=ether2-master 

 2    chain=dstnat action=dst-nat to-addresses=192.168.88.12 to-ports=80 protocol=tcp dst-address=10.7.8.141 dst-port=80

But I can’t understand logic of

chain=srcnat action=masquerade protocol=tcp dst-address=192.168.88.12 out-interface=ether2-master

Why IP of WebServer is forwarding to the same Lan

dst-address=192.168.88.12 out-interface=ether2-master

Thank you for help!

You try to connect from NB to server and it creates packet 10.7.8.148->10.7.8.141. It goes to router, it applies dstnat rule to forward it to server’s real address and it changes packet to 10.7.8.148->192.168.88.12. If you didn’t have srcnat rule, it would reach the server like this, it would try to reply and because it (probably) doesn’t have static route to 10.7.8.148, it would send it using its default gateway, which you write is not this router. Your srcnat rule further changes packet to 192.168.88.1->192.168.88.12. Server knows where to find 192.168.88.1 (in local subnet), so it sends reply packet to the right router. And router knows to which connection it belongs, so it changes everything back and NB gets reply packet from 10.7.8.141 as it expects.

yes. that’s right i was checking on web server with wireshark. but what exactly expression says on human language?

chain=srcnat action=masquerade protocol=tcp dst-address=192.168.88.12 out-interface=ether2-master

All tcp traffic from ip address 192.168.88.12 which comes from ether2-master have to be masquarated? Can you approve my interpretation?
I also got working when excluded

out-interface=ether2-master

And works like that

dst-address=192.168.88.0/24 out-interface=ether2-master

It’s all tcp traffic to 192.168.88.12 which leaves router via ether2-master, and that’s to be masqueraded. In your case, if 192.168.88.0/24 is on ether2-master, out-interface is reduntant, because it won’t go anywhere else.

Oh, yes! For sure all tcp to 192.168.88.12 …
Thanks, I got it.