Physical Connection Strategy
The most critical step in transforming a MikroTik router into a switch is the physical cabling. Most consumer-grade routers have distinct WAN and LAN ports, but MikroTik devices like the hEX series or RB series often treat all Ethernet ports equally unless software-defined separation is applied. To ensure seamless integration with your existing network, you should avoid using the port labeled "WAN" if it is hardcoded for PPPoE or specific routing protocols. Instead, plug the ethernet cable coming from your main router or upstream switch directly into any of the standard LAN ports, typically numbered 2 through 5 on a 6-port unit. This physical connection ensures that the MikroTik device receives an IP address from your main network’s DHCP server rather than trying to assign one itself. If you connect the cable to a port designated for internet access in the default configuration, the device might attempt to establish a new gateway route, which will break the switch functionality. By treating all ports as part of the same local segment, you create a single broadcast domain. This approach mirrors how a standard unmanaged switch operates, where every plugged-in device sees every other device on the network regardless of the physical port used. For more details on connecting routers to switches, see How to Connect an Eero Pro 6e Router to a Network Switch.Disabling Routing and DHCP Services
Once physically connected, you must strip away the router’s identity. Access the MikroTik WebFig interface via a browser using the default IP address, usually 192.168.88.1. Navigate to the IP settings section. Here, you will find the list of addresses assigned to interfaces. Select the IP address associated with your LAN interface (often ether2, ether3, etc.) and delete it. Without an IP address on the LAN side, the device cannot perform Layer 3 routing between networks. Next, navigate to the IP > DHCP Server menu. Disable the DHCP server service entirely. If the DHCP server remains active, it may attempt to hand out IP addresses in a different subnet range than your main router, causing IP conflicts or connectivity failures for clients. You should also check the IP > Firewall menu. While not strictly necessary for basic switching, disabling the default firewall rules prevents potential blocking of traffic between LAN ports if strict security policies were previously enabled. Ensure that the interface list does not mark any LAN ports as "unreachable" or isolated. The goal is to make the MikroTik invisible at the IP layer, functioning only as a transparent bridge for MAC addresses.Configuring Wireless as a Bridge
With the wired side configured as a pure switch, you can now enable WiFi. Go to the Wireless tab in WebFig. Select your wireless interface (usually wlan1 or wlan2) and click the Configure button. In the Basic Settings, choose the mode as "ap bridge" or "bridge." This mode tells the radio to operate at Layer 2, bridging wireless frames directly to the Ethernet bridge. Do not select "station" or "client" modes, as those are intended for connecting wirelessly to another network. In the Frequency and Band settings, choose a frequency that minimizes interference with your main router. If your main router uses channel 6 on 2.4GHz, consider setting the MikroTik to channel 1 or 11. It is highly recommended to use a different SSID (network name) for this extended WiFi zone. While some users try to match the SSID exactly for roaming, MikroTik’s default wireless driver does not support seamless 802.11r/k/v roaming out of the box. Using a distinct name like "HomeWiFi_Ext" helps users manually connect to the strongest signal. Set a strong WPA2-PSK password identical to your main network if you want consistent credentials, though technically any valid password works since the device is just passing traffic.Bridging Ethernet and WiFi Interfaces
The final technical step is linking the wireless radio to the Ethernet LAN ports. Navigate to Bridge > Bridges and create a new bridge named "bridge-local" or similar. Then go to Bridge > Ports. Add both your LAN Ethernet interfaces (ether2, ether3, etc.) and the wireless interface (wlan1) to this bridge. This action creates a single logical switch board inside the MikroTik OS. Any packet entering via WiFi is instantly forwarded to the Ethernet ports and vice versa. Verify the configuration by plugging a laptop into one of the LAN ports and connecting via WiFi simultaneously. Both devices should receive IP addresses from your main router’s DHCP pool. They should be able to ping each other and access the internet without restriction. If you experience slow speeds, check the wireless channel width; sticking to 20MHz on 2.4GHz often provides better stability in dense environments. For troubleshooting connection drops during this process, refer to Troubleshooting Ethernet Connection Issues.Frequently Asked Questions
Can I use the WAN port for this setup?
It depends on the model, but generally, you should avoid the port labeled WAN if it has hardcoded PPPoE client settings enabled. On many MikroTik devices, all ports are equal at the hardware level, so using ether2-5 is safer to prevent accidental routing configurations.
Why do I lose internet access after disabling DHCP?
You likely deleted the IP address from the management interface or failed to bridge the ports correctly. Ensure you still have access to the device via the initial management IP, and verify that the bridge includes both LAN and WiFi interfaces.
Will this setup support VoIP phones?
Yes, because the device acts as a transparent switch, VLAN tags and QoS markings from your main router will pass through unchanged. However, ensure your main router handles the QoS prioritization, as the MikroTik bridge ignores these packets by default.
How do I update the firmware without losing config?
Use the System > Packages menu to download the latest version. Install it while keeping the current configuration intact. Always backup your configuration before major updates to restore settings if the bridge fails to initialize.
Is there a risk of network loops?
Only if you accidentally connect two LAN ports back to each other or to the same uplink twice. Enable Spanning Tree Protocol (STP) in the Bridge settings if you plan to daisy-chain multiple such switches to prevent broadcast storms.