In case that MikroTik detect that DHCP, it will completely ignore it.

If we already have any DHCP server in that network segment, we should specify its MAC address(es) in the field named Valid Servers. In such case, your MikroTik device will detect and only internally log any new DHCP server in the network. You can access this feature using the command line with ip dhcp-server alert.Ĭlick on the button to add a new DHCP alert:Īt least, you need to choose an appropriate network interface and alert timeout. To access this feature, in the WinBox GUI: This LAN segment even can be one VLAN inside the network. You should also write down the MAC address(es) of your DHCP server(s) and the LAN segment for which you want to set monitoring. By default, every MikroTik Routerboard has this packet installed and enabled. The pre-requirement is to have the DHCP package installed and enabled on your device. Just turn this port off and your network is safe again.Īs always, we can enable this feature using the command line, the WinBox or WebFig GUI. Once located, you can block its network access with the remote port administration. However, you can locate this machine in the network using the switch MAC address table.

This is the option that should be implemented on your network switches. You can’t use the MikroTik router to actively block such machine. When an alert occurred, you will be informed about the MAC address (and a few more details) of that machine. Even better, it can send you an email on such detection. Every MikroTik device with the DHCP server service can be used to search your network for any rogue DHCP server.

Mikrotik client hang on dhcp address