Masquerading is a form of source NAT (src-nat) where the router dynamically replaces the source address of outgoing packets with the IP address of the router’s outgoing interface. This is commonly used when internal LAN clients access the internet through a single public IP.
Key points for masquerade configuration:
Use chain=src-nat (because it modifies the source address)
Use action=masquerade
Specify the out-interface (i.e., the WAN interface)
MTCNA Course Material – NAT Section:
“To configure masquerading, use chain=src-nat and action=masquerade. Specify out-interface to define the traffic direction.”
René Meneses MTCNA Study Guide – NAT Examples:
“Masquerade automatically uses the IP address of the specified out-interface. Required parameters: chain=src-nat, action=masquerade, out-interface.”
MikroTik Wiki – Source NAT / Masquerade:
“Masquerade is a special form of src-nat. You must use it in chain=src-nat and define the out-interface for which NAT will be applied.”
Option A: Incorrect action=accept (used in filter rules, not NAT)
Option C: in-interface is not applicable here
Option D: chain=dst-nat is used for destination NAT, not source NAT
Only Option B is fully correct.
Final Answer: BQUESTION NO: 94 [Tools]
In which situations can Netinstall NOT be used to install a RouterBOARD?
A. The router does not have an operating system
B. The router is connected only to a wireless network
C. You do not know the password of the router
D. The router is connected only to a secondary Ethernet port
Answer: B
Netinstall works over a wired Ethernet connection and uses PXE or Etherboot to install RouterOS over the network. It cannot function over wireless, as wireless interfaces do not support PXE booting or Netinstall protocols.
MTCNA Course Material – Netinstall Overview:
“Netinstall requires a direct Ethernet connection between the PC and the router. Wireless interfaces are not supported for Netinstall procedures.”
René Meneses MTCNA Guide – Netinstall:
“Netinstall only works over Ethernet. You cannot Netinstall a device connected only through Wi-Fi.”
MikroTik Wiki – Netinstall Prerequisites:
“Router must be connected via Ethernet. Wireless and USB interfaces are not supported.”
Other options:
A: This is a typical use case (installing RouterOS when OS is missing)
C: Netinstall bypasses password (not needed)
D: Netinstall can work via any Ethernet port, provided it's accessible
Final Answer: BQUESTION NO: 95 [Monitoring and Logging]
MikroTik RouterOS is sending logs to an external syslog server. Which protocol and port is used by RouterOS for sending logs (by default)?
A. UDP 514
B. UDP 21
C. UDP 113
D. TCP 110
Answer: A
RouterOS uses the industry-standard syslog protocol for remote logging. By default, syslog uses UDP port 514.
MTCNA Course Material – Logging Section:
“For sending logs to a remote syslog server, RouterOS uses the syslog protocol on UDP port 514 by default.”
René Meneses MTCNA Guide – Monitoring & Logging:
“External logging is done using UDP port 514, which is the standard syslog protocol port.”
MikroTik Wiki – Logging Configuration:
“To send logs to a remote server, configure an action of type remote with a remote address and use UDP port 514 unless otherwise changed.”
Other ports:
Only UDP 514 is correct.
Final Answer: AQUESTION NO: 96 [RouterBOARD Hardware]
Can you manually add drivers to RouterOS in case your PCI Ethernet card is not recognized, and you suspect it is a driver issue?
A. Yes
B. No
Answer: B
RouterOS is a closed, embedded Linux-based system. It does not support adding custom drivers or compiling modules manually. You must use supported hardware that is natively compatible with RouterOS.
MTCNA Course Material – RouterBOARD Compatibility:
“RouterOS supports a fixed set of drivers. You cannot install third-party drivers or modules.”
René Meneses MTCNA Guide – Hardware Limitations:
“Custom drivers cannot be added to RouterOS. Use only supported network interface cards as listed by MikroTik.”
MikroTik Wiki – Hardware Support:
“RouterOS does not allow manual driver installation. All drivers are precompiled and built into the system image.”
Therefore, if your PCI Ethernet card is not recognized, you must replace it with a compatible model — you cannot add a driver manually.
Submit