Skip to content
MikroTik RouterOS Docs

MAC Server Configuration

For the impatient: restrict MAC access to LAN interfaces only for security.

/tool mac-server set allowed-interface-list=LAN
/tool mac-server mac-winbox set allowed-interface-list=LAN
/tool mac-server ping set enabled=no

Verify with:

/tool mac-server print
/tool mac-server mac-winbox print

What this does: MAC Server provides Layer 2 management access to RouterOS without requiring IP configuration. It includes MAC-Telnet (CLI), MAC-Winbox (GUI), and MAC Ping services. This is essential for initial router setup or recovery when IP connectivity is unavailable.

When to use this:

  • Initial router configuration before IP is set
  • Recovery when IP configuration is broken
  • Accessing routers in unknown network state
  • Emergency management access on trusted networks

Prerequisites:

  • Direct Layer 2 connectivity (same broadcast domain)
  • Winbox application (for MAC-Winbox)
  • Another MikroTik router (for MAC-Telnet between routers)
ServicePurposeAccess Method
MAC-TelnetCommand-line accessAnother MikroTik or Linux client
MAC-WinboxGraphical Winbox accessWinbox application
MAC PingRespond to MAC-level pingsMAC ping utility

View current MAC server settings.

/tool mac-server print
/tool mac-server mac-winbox print
/tool mac-server ping print

Default output:

allowed-interface-list: all

By default, MAC access is enabled on all interfaces, including WAN.

Create an interface list for trusted management interfaces.

/interface list add name=MGMT
/interface list member add list=MGMT interface=bridge

Limit MAC-Telnet to management interfaces only.

/tool mac-server set allowed-interface-list=MGMT

Limit MAC-Winbox to management interfaces only.

/tool mac-server mac-winbox set allowed-interface-list=MGMT

Disable MAC ping responses for additional security.

/tool mac-server ping set enabled=no

Confirm settings are applied.

/tool mac-server print
/tool mac-server mac-winbox print

Expected output:

allowed-interface-list: MGMT

Most default configurations include a “LAN” interface list:

/tool mac-server set allowed-interface-list=LAN
/tool mac-server mac-winbox set allowed-interface-list=LAN

For maximum security in production environments:

/tool mac-server set allowed-interface-list=none
/tool mac-server mac-winbox set allowed-interface-list=none
/tool mac-server ping set enabled=no

Enable MAC access only on specific physical ports:

/interface list add name=mac-access
/interface list member add list=mac-access interface=ether1
/interface list member add list=mac-access interface=ether2
/tool mac-server set allowed-interface-list=mac-access
/tool mac-server mac-winbox set allowed-interface-list=mac-access

From another MikroTik router, connect using MAC address:

/tool mac-telnet B8:69:F4:7F:F2:E7

Specify interface (v7.22+):

/tool mac-telnet B8:69:F4:7F:F2:E7 interface=ether1

Discover routers on the network:

/tool mac-scan ether1

Expected output:

MAC-ADDRESS ADDRESS AGE
B8:69:F4:7F:F2:E7 0.0.0.0 3
4C:5E:0C:12:34:56 0.0.0.0 5
  1. Open Winbox
  2. Click “Neighbors” tab
  3. Select router by MAC address
  4. Enter credentials and click “Connect”
/tool mac-server print

Expected: Shows restricted allowed-interface-list.

/tool mac-server mac-winbox print

Expected: Shows restricted allowed-interface-list.

From Winbox Neighbors tab, verify router appears only when connected to allowed interface.

SymptomCauseSolution
Cannot connect via MAC-WinboxMAC-Winbox restrictedCheck allowed-interface-list includes your interface
Router not in Winbox NeighborsDifferent broadcast domainEnsure Layer 2 connectivity (same VLAN/switch)
“Could not connect” errorService disabledSet allowed-interface-list to include interface
Windows can’t find routerFile and Print Sharing disabledEnable in Windows network settings
MAC-Telnet works, Winbox doesn’tDifferent servicesConfigure both MAC-Telnet AND MAC-Winbox
Connection drops immediatelyVersion mismatchUpdate Winbox and RouterOS
Multiple NICs cause issuesWrong adapter usedDisable unused network adapters

Security Considerations

  • MAC access bypasses IP firewall - Layer 2 traffic is not filtered by /ip firewall
  • Default enables on ALL interfaces - Including WAN, which is dangerous
  • No IP-based access control - Any device on same L2 segment can attempt connection
  • Always restrict to trusted interfaces - Never allow MAC access on public/WAN interfaces
  • Consider disabling in production - Use IP-based access (SSH, Winbox over IP) instead
  • IP Neighbors - neighbor discovery protocols
  • RoMON - remote management overlay network
PropertyTypeDefaultDescription
allowed-interface-liststringallInterface list where service is enabled

Special values:

  • all - Service on all interfaces (insecure default)
  • none - Service completely disabled
  • listname - Service only on interfaces in specified list
PropertyTypeDefaultDescription
enabledyes/noyesEnable MAC ping responses
CommandDescription
/tool mac-server setConfigure MAC-Telnet server
/tool mac-server printShow MAC-Telnet settings
/tool mac-server mac-winbox setConfigure MAC-Winbox server
/tool mac-server mac-winbox printShow MAC-Winbox settings
/tool mac-server ping setConfigure MAC Ping
/tool mac-server ping printShow MAC Ping settings
/tool mac-telnet <MAC>Connect to remote router via MAC
/tool mac-scan <interface>Scan for MAC-accessible devices