In particular situation it’s just for example. Basically this rule will make dst-nat from WAN network to host 192.168.88.x and port 80, you can modify host and port as you need it.
Also as “Anumrak” said, you can use static routes on both ends to achieve net to net connection.
yes I got that this is an example.
In my case, I need a Unifi access point to assign DHCP addresses from the LAN pool (192.168.88.x), but to be able to check on the UniFi controller residing on WAN network (192.168.0.x).
So, I added this: chain=dstnat action=accept to-addresses=192.168.88.246 protocol=tcp dst-address=192.168.88.246 in-interface=ether1 src-port=8080
dst-port=8080 log=no log-prefix=“” and the unifi device (192.168.88.246) can be visible in the controller.
The example you mentioned throws an error: mikrotik failure: to-ports valid only for tcp/udp/sctp/dccp
I cannot add route to the WAN net, so I have to work only on my side.