ok, I know that it’s possible to make it by hand, but IMHO it should be more simple like checkbox in dst-nat rule.
What exactly should this checkbox stand for? For a whole complex set of rules that everyone uses in different ways?
Look at this: https://help.ubnt.com/hc/en-us/article_attachments/202830350/original.png
… so it’s possible to implement. Maybe the checkbox-idea isn’t ideal for all possibilities, but the wizard like for hotspot setup should be more universal.
I understand you. Nice picture. Easy to tick on or off, as you wish. Everyone can understand what is wan and what is lan and nothing more is needed. Everything is hidden in background. You do not know what will happen to each single packet under what conditions and so. Hairpin. Just yes or no. But that is not how complex networks operate. Well, maybe it could be done so in quickset in one single standard way realated to default config, for those that never touch any other part of menu than quickset. It might be working under such condition.
But the normal world is not so easy and schematic. There are many wans, many lans, some peering networks around, tunnels here and there, something should be natted, something routed untouched, something should be reflected back by hairpin… very complicated for other than “home ap” routing mode.
I am known here not to be a fan of quickset, but saying now:
Yes I am with him. Mikrotik, please, put the hairpin single tickbox into quickset and let me to remove the quickset fully from my devices!
I agree with you that quickset should be made a separate package that can be removed, or some checkbox in the system menu can
be ticked to remove quickset from the landing page. It is too dangerous to have there lurking all the time.
Also, it could be a good idea to expand quickset with options as described here, maybe transforming it into the “KISS” config found on
most customer routers. But I fear that this is only possible when the full configuration options are made unavailable when quickset
is enabled.
I agree with jarda!
What if e.g. RB2011 is used with two separate public addresses and one switch group has its own WAN and LAN interfaces and the second switch ports group has different WAN and LAN ports ?
How to choose WAN1 and WAN2 for particular LAN1 and LAN2 ?
I believe, that for Mikrotik devs the impossible tasks just doesn’t exist 
. Look for example at complexity of hotspot wizard.
Everything is possible, only the resources are scarce so their utilisation needs to be optimised by priority…
Hairpin NAT is simple. It’s not check box simple but we need something to justify the MTCNA’s and RE’s.
It’s a 1 liner in dst-nat and then you just need to make sure you create your port forwards properly.
ROS7
SCNR