MikroTik VLAN Setup for a Small Office in Kenya
An office network often starts with one router, one switch and a Wi-Fi access point. As the business grows, staff computers, guest phones, printers and CCTV cameras all end up sharing the same network. That makes it harder to control access and troubleshoot problems.
A VLAN separates devices into logical networks while allowing them to share suitable physical equipment. For example, staff can access office printers, guests can access the internet, and cameras can communicate with their recorder. The router and firewall determine which networks may communicate with each other.
This guide explains how to plan a MikroTik VLAN setup for a small office in Kenya, connect the supporting equipment and test that each group has the right access. If you are choosing hardware for a new installation, explore our MikroTik router range first.
[Insert the first generated image here: office network cabinet]
What is a VLAN?
A virtual LAN, usually called a VLAN, divides a physical network into separate logical groups. Devices can connect through the same managed switch without necessarily sharing the same local network.
Consider an office with employees, visitors and CCTV cameras. Without separation, a visitor connected to Wi-Fi might be on the same network as a printer or camera recorder. With VLANs, the office can place those devices in different groups and create rules governing access between them.
A VLAN by itself is not a complete security policy. If the router allows unrestricted traffic between VLANs, devices in one group may still reach devices in another. Effective separation requires the correct switch port settings, IP addressing and firewall rules.
MikroTik explains these functions in its RouterOS VLAN documentation and bridge VLAN table guide.
Plan your office networks first
Before opening WinBox or changing a router setting, list the devices that need network access. Identify staff computers, printers, wireless access points, guest devices, cameras, recorders and network management equipment.
A small office could start with the following plan:
| Network | Example VLAN ID | Example IP range | Purpose |
|---|---|---|---|
| Staff | 10 | 192.168.10.0/24 | Staff computers and approved office resources |
| Guest | 20 | 192.168.20.0/24 | Visitor internet access |
| CCTV | 30 | 192.168.30.0/24 | Cameras and recording equipment |
| Management | 40 | 192.168.40.0/24 | Router, switch and access point administration |
These VLAN IDs and IP ranges are examples. Check the addresses your business already uses before adopting them.
You may not need all four VLANs. A very small office might begin with staff and guest networks. Add a separate CCTV or management network when you have a clear reason and the equipment to support it.
Decide who should access what
The most useful question in a VLAN project is: Which devices actually need to communicate?
Staff may need internet access and a printer. Guests may need internet access only. A CCTV recorder needs to communicate with cameras, while selected staff may need to view the recorder. Only administrators should reach the management interfaces of the router and switches.
Write those requirements down before creating firewall rules:
| Source network | Destination | Intended access |
|---|---|---|
| Staff | Internet | Allow |
| Staff | Approved office printer | Allow |
| Staff | CCTV recorder | Allow if required |
| Guest | Internet | Allow |
| Guest | Staff and CCTV networks | Block |
| Guest | Router management | Block |
| CCTV | Management network | Block unless specifically required |
| Administrator device | Router and switches | Allow required management access |
This table is a planning example, not a ready-made RouterOS firewall configuration. Your rules must account for the existing firewall, interface lists and other services on your network.
Understand access ports and trunk ports
The managed switch must know which VLAN belongs on each connection.
An access port generally connects to a device such as a staff computer or camera. The device does not need to understand VLAN tags; the network equipment places its traffic into the assigned VLAN.
A trunk port carries more than one VLAN between compatible network devices. The connection between the MikroTik router and a managed switch may be a trunk. The connection to an access point may also be a trunk if the access point broadcasts both staff and guest Wi-Fi networks.
Imagine an access point broadcasting Office-Staff and Office-Guest. The access point, switch and router must agree on the VLAN assignment for each Wi-Fi network. Configuring the router alone is not enough.
[Insert the second generated image here: technician connecting switch cables]
Give each network the correct IP addresses
Each routed VLAN needs an IP subnet and a gateway. Using the earlier example, the router might provide these gateways:
| Network | Example gateway |
|---|---|
| Staff | 192.168.10.1 |
| Guest | 192.168.20.1 |
| CCTV | 192.168.30.1 |
| Management | 192.168.40.1 |
Devices should receive addresses belonging to their own network. A guest phone, for example, should receive an address from the guest subnet—not the staff subnet.
If RouterOS provides DHCP, make sure each DHCP server and its network settings correspond to the correct VLAN interface. MikroTik’s DHCP documentation is useful when planning and checking those settings.
An incorrect IP address is a valuable troubleshooting clue. If a guest phone receives a staff address, inspect the access point configuration, switch port and VLAN tagging before changing unrelated firewall rules.
Plan router and switch connections
Draw a simple connection map before deployment. Record which router port connects to the managed switch, which switch ports serve staff computers or cameras, and which ports feed access points.
Label the physical cables as you install them. A port labelled “Guest AP” or “CCTV Recorder” is easier to troubleshoot than an unidentified cable in a crowded cabinet.
Also identify the port or network you will use to administer the router during the change. Enabling bridge VLAN filtering with incorrect membership can interrupt management access. Keep a working backup and a recovery method available.
RouterOS behaviour and hardware offloading vary by device. Check the MikroTik bridging and switching documentation for the exact model you intend to use.
Configure in a controlled order
A practical installation follows this sequence:
- Document the existing network. Record WAN and LAN ports, IP ranges, DHCP services, firewall rules and switch connections.
- Save the working configuration. Keep a backup and configuration export somewhere secure outside the router.
- Confirm management access. Know how you will reconnect if a VLAN change interrupts your current session.
- Configure the managed switch and access points. Assign access ports and trunk links according to your plan.
- Configure VLAN interfaces and gateways. Give routed VLANs the intended IP addresses.
- Set up DHCP where needed. Confirm each device group receives addresses from the right subnet.
- Apply the firewall policy. Permit required traffic and restrict access between groups.
- Review bridge VLAN membership. Check tagged and untagged ports before enabling filtering.
- Test using actual devices. Connect a staff computer, guest phone and CCTV device.
- Save and document the finished setup. Create a new backup after successful testing.
MikroTik’s configuration management documentation explains backups and Safe Mode. These are useful protections when making changes, particularly to a router you manage remotely.
Test more than internet access
A guest phone reaching the internet does not prove the VLAN setup is correct. You also need to confirm that it cannot reach restricted office resources.
From a staff device, check its IP address, internet access, printer access and any approved business systems.
From a guest device, check its IP address and internet access. Then confirm it cannot reach the office printer, CCTV recorder or router management interface.
From a CCTV device, check that it communicates with the recorder and does not have unintended access to staff or management systems.
Finally, use an administrator device to verify that authorised management access still works. Record the result of each test. If something fails, check the cable and port assignment, VLAN tagging, IP address, gateway and firewall rule in that order.
Common MikroTik VLAN mistakes
Assuming VLANs automatically block access
Separate subnets do not necessarily prevent traffic between them. Review the router’s firewall rules and test the intended restrictions.
Forgetting to configure the managed switch
The router cannot correct a switch port that places a device in the wrong VLAN. Confirm the configuration at every point along the connection.
Using an access point that does not support the plan
If you want staff and guest Wi-Fi on separate VLANs through one access point, check that the exact access point model supports that configuration.
Losing router management access
Changing VLAN filtering or management network settings remotely can disconnect the administrator. Back up first and confirm a recovery route.
Copying commands from another network
A command may refer to different interface names, bridge settings or VLAN IDs. Adapt settings to the documented network you are installing.
Choosing equipment for a small-office VLAN network
The right hardware depends on the number of ports, internet speed, connected users, Wi-Fi coverage and features you expect to add. Plan the network before choosing a model.
You can compare the MikroTik router options on our homepage and browse MikroTik equipment at Orbitlink Solutions, Tawa and Reisen SEO. If you are evaluating one specific model, see the RB5009UG+S+IN listing at Jupitaz. Confirm the exact model, interfaces and current availability before ordering.
If your network also sells internet access to tenants or hotspot users, you may need subscriber and payment management alongside the networking setup. Tajira is an example of an ISP billing platform to evaluate for that separate business requirement.
Frequently asked questions
Do I need a managed switch for VLANs?
If different device groups share a switch and require separate VLAN assignments, you generally need a switch that supports the necessary VLAN configuration. Check the exact switch model and your port plan.
Can staff and guest Wi-Fi use one access point?
Yes, if the access point supports multiple Wi-Fi networks with the required VLAN settings. The switch connection and router must also be configured consistently.
Will VLANs increase my internet speed?
VLANs organise network traffic and access. They do not increase the speed supplied by your internet provider. Network performance also depends on the router, switch, Wi-Fi and configuration.
Should CCTV be on its own VLAN?
A separate CCTV VLAN can make access to cameras and recorders easier to control. Whether it is worthwhile depends on the size of the installation and who needs to view or manage the equipment.
Can I introduce VLANs to an office that already has users online?
Yes. Document the existing setup, make a backup and schedule the change. Test each device group before considering the migration complete.
Build the network around your access requirements
A good office VLAN setup starts with a clear list of devices and the connections they need. Once you know which users require staff resources, guest internet, CCTV viewing and management access, you can choose the hardware and configure the network around those requirements.
Explore our MikroTik router range when selecting the gateway. If you are new to RouterOS, read our MikroTik configuration guide for the basic WAN, LAN, DHCP and firewall concepts before adding VLANs.