3 ms·
It may sound strange, but for Mikrotik, I find it more productive to concentrate on setting them up via CLI. It's certainly more trainable. CLI for Port Forwar
by benjohnson 6y ago
It may sound strange, but for Mikrotik, I find it more productive to concentrate on setting them up via CLI. It's certainly more trainable.
CLI for Port Forward:
/ip firewall nat add chain=dstnat dst-port=1234 in-interface=ether1-gateway action=dst-nat protocol=tcp to-address=192.168.1.1 to-port=1234
VS having to document the same task in the GUI:
IP->Firewall->Nat->
Add New
General Tab
Chain: dstnat
Protocol: TPC
Dst. Port: Port
In. Interface: ether1-gateway
Action Tab
Action: dst-nat
To Address: IP address of Server
To Port: Port # of Service
- bombcar 6y agoThe CLI tab-completion is great - you can figure out most of what you need to do just by looking at it. Highly worth getting one to try out.
- eecc 6y agoYup, very nice router/switch. If anyone could forward a properly documented configuration to make the Apple AirPort guest network work I'd be ever grateful.
- locusm 6y agoSame reason I like EdgeRouters and VyOS
- robocat 6y agoThe benefit of the GUI is that it documents what has been changed: in the GUI there is a list of port forwards. With the CLI you either need to document it yourself, or you need to know to query if there are any port forwards. That can be a problem if there is more than one person responsible for the network, or if someone else needs to inherit your setup. Documentation of configuration sometimes isn’t an issue on your own home system because you generally have a high level memory of what changes you made and their purpose. Conversely I still struggle sometimes with Ubuntu because I customise my configuration using command line tools, and I find keeping track of those changes or the implications of those changes is difficult.