How to just open ports

RouterOS Beginner Basics
21

Hellop Guys,

I have a problem and I hope we can solve I apologize in advance for my english .
So I want to open a port on Mikrotik and have introduced this command to the terminal,

  • /ip firewall nat add chain=dstnat dst-port=80 action=dst-nat protocol=tcp to-address=192.168.0.141 to-port=80

The command was accepted in terminal mikrotik ,until everything is fine here
Now I’m opening an internet explorer and introducing WAN IP ie 31.5.xxx.xxx ,and the error appears

This site can’t be reached.
Darn mention that XamPP is running for apache
And the strange thing is that I look inside Winbox at the firewall and see it traffic but the problem is that the website does not start for what reason

Can someone help me solve this problem
thank you for understanding
I’m waiting for a soul-to-mouth response

22

What happens if you locally point your internet browser to http://192.168.0.141:80 does the apache server answer? post

/ip export
/ip route print
/ip address print
23

On Ip this means that it means http://192.168.0.141:80
Is functional but Ip Wan ip exterior does not work

/ip address print
Flags: X - disabled, I - invalid, D - dynamic

ADDRESS NETWORK INTERFACE

0 192.168.0.1/24 192.168.0.0 Ether2-Master
1 D 31.5.xxx.xxx/24 31.5.xxxx.x Ether - WAN

24

You need to setup hairpin NAT
https://wiki.mikrotik.com/wiki/Hairpin_NAT

By default, when you are internal, you can’t connect to your internal website via your external IP address.

This is because when you connect to 31.5.xxx.xxx, the packets are redirected to your webserver without changing (NATing) the source and destination addresses. So your web server gets the packet from 192.168.0.x and attempts to reply directly to the computer. Your computer is expecting the reply to come from 31.5.xxx.xxx. Since it is not, it gets dropped. Follow the link above. It explains how both the source and destinations need to be changed and how all traffic to your webserver will have to go through the Mikrotik.

I find hairpin NAT to be tedious. I find it easier to use URLs and override DNS. If www.yourdomain.com points to 31.5.xxx.xxx, you can override the DNS in the Mikrotik to point www.yourdomain.com to 192.168.0.x Then all internal dns queries resolve www.yourdomain.com to your internal IP.