Druvis shows you how to configure Static a.k.a. One-to-One NAT in RouterOS. Even though it is the most basic NAT, there is a little twist due to the src-nat - dst-nat paradigm.
Should show limiting the dstnat rule with a dst port and a to-port to ensure one is only allowing the "right traffic" as much as possible. Also suggest adding a source-address-list to the dstnat rule as most should have a fixed static WANIP or a dynamic WANIP ( and free dyndns names/urls ) are available to resolve to their WANIP.
Our ISP provides 1 uplink with 5 static IPs. How do I get the outbound traffic to use the same WAN Ip it came in from. I tried a basic 1:1 NAT rule but it did not work.
The presenter has consistently avoided using dynamic WAN Ips in his videos. Dynamic WANIP would take longer to present because the config becomes more complex and one may have to get into describing perhaps scripting and/or mangling etc..... Thus suggesting, that Druvis make a separate video that addresses the ways in many of his videos one would have to adjust the approach for dynamic WANIPs........... Or MT can simply state, Mikrotik Devices are only for users with static WAN IPs. :-)
What setup relying on dynamic WAN IP would be most useful to people and therefore should be demonstrated? Masquerade, for example, will adjust automatically whenever the public IP gets changed.
@@mikrotik True, but there are linkages between dstnat rules, firewall rules and also hairpin nat scenarios. In this case one to one, its simple as you state. I guess one could state, that these examples are very much quarantined from the various actual scenarios people might be dealing with. Impossible to cover everyone so your focusing on the core functionality of how it works and its up to the reader to adapt to their own situation.
Can someone explain how to create port exception for device management when nat 1:1 is used? I would like to reach mikrotik device via public ip and have one to one nat on it.
Should show limiting the dstnat rule with a dst port and a to-port to ensure one is only allowing the "right traffic" as much as possible. Also suggest adding a source-address-list to the dstnat rule as most should have a fixed static WANIP or a dynamic WANIP ( and free dyndns names/urls ) are available to resolve to their WANIP.
Our ISP provides 1 uplink with 5 static IPs. How do I get the outbound traffic to use the same WAN Ip it came in from.
I tried a basic 1:1 NAT rule but it did not work.
Great video. Tx for that. Regarding the ‘public ip’ address. You aleays refer to static public ip address. What about the dynamic public ip address?
Hi everyone!
At other vendors there is a possibility to delete one word at once Ctr+W, but is there a possibility to do that in Mikrotik as well ?
❤❤❤❤❤ this is Mikrotik for dummies like me.
love this cind of videos
The presenter has consistently avoided using dynamic WAN Ips in his videos. Dynamic WANIP would take longer to present because the config becomes more complex and one may have to get into describing perhaps scripting and/or mangling etc..... Thus suggesting, that Druvis make a separate video that addresses the ways in many of his videos one would have to adjust the approach for dynamic WANIPs........... Or MT can simply state, Mikrotik Devices are only for users with static WAN IPs. :-)
What setup relying on dynamic WAN IP would be most useful to people and therefore should be demonstrated? Masquerade, for example, will adjust automatically whenever the public IP gets changed.
@@mikrotik True, but there are linkages between dstnat rules, firewall rules and also hairpin nat scenarios. In this case one to one, its simple as you state. I guess one could state, that these examples are very much quarantined from the various actual scenarios people might be dealing with. Impossible to cover everyone so your focusing on the core functionality of how it works and its up to the reader to adapt to their own situation.
Can someone explain how to create port exception for device management when nat 1:1 is used? I would like to reach mikrotik device via public ip and have one to one nat on it.