MikroTik
MikroTik routing, VLANs and remote access for SMEs: prepare documented configurations, security and ongoing network support in Switzerland with Sunitech.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais
MikroTik can address routing, segmentation and connections between sites. RouterOS combines functions including routing, firewalling and VPNs. That flexibility is useful when a network must follow specific requirements, but it calls for an understandable configuration. For an SME in French-speaking Switzerland, we start with applications and locations to connect, identifying necessary paths, restrictions and dependencies on your service provider.
Plan MikroTik routing around existing networks, connections between sites and business applications, documenting expected traffic paths and testing them before making changes that could affect access to important shared services.
Define the communications required on MikroTik equipment, remove openings without an identified purpose and verify rules with application owners, while maintaining a controlled administrative recovery route for authorised support staff.
Review remote connectivity needs against the functions available in the relevant MikroTik version, then prepare access, routing and removal procedures suited to the authorised people and the services they need to reach.
Identify applications affected by congestion before configuring MikroTik traffic priorities, then observe their behaviour under representative conditions rather than applying identical settings to every business regardless of its actual network use.
Select MikroTik information that helps operate the network, organise alerts and name the people who will review them, connecting technical events with the incidents and interruptions actually experienced by business teams.
Maintain an inventory of RouterOS versions, retain the configurations needed for recovery and prepare MikroTik updates with tests and rollback arrangements appropriate to the operational importance of the equipment being changed.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Identify sites, equipment, traffic and dependencies before defining priorities.
Prepare changes, test configurations and organise commissioning.
Assess usage, coverage areas and mobility needs. The required measurements are agreed during scoping.
Separate uses, restrict traffic and define access rules with the people responsible.
Agree monitoring checks, updates and incident-handling arrangements.
Document the network and plan its next developments with your teams.
We start with your teams’ needs, business applications and organisational constraints.
Share client files between colleagues, with appropriate access and documents that are easy to find.
Keep tills and connections working, including across multiple shops.
Protect patient records and maintain the tools needed for consultations.
Connect the office and the workshop, secure equipment and prepare for recovery after an incident.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Defined areas and needs, with coverage to be checked on site.
Traffic rules and separate access according to usage.
Inventoried equipment and checks suited to the required service.
Updates and changes prepared with the people involved.
Useful documentation for planning replacements and new requirements.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
Selection depends on interfaces, traffic, tunnels and enabled processing. Port count alone cannot size the equipment. We record the model, software version and applicable licences before comparing options. An IT audit can also recover the reasoning behind existing rules. Addresses used at different sites need examination to prevent overlaps that would complicate connections.
We prepare addressing, VLANs, filtering rules and essential services. Administrator access is restricted, accounts identified and unnecessary services disabled after checking dependencies. A configuration backup and rollback procedure precede deployment. For a WireGuard tunnel, we define peers, authorised networks and key management. Tests cover permitted traffic as well as traffic that must remain blocked.
Rules added incident by incident become difficult to hand over. We favour useful comments, a dependency inventory and recorded changes. Performance varies with enabled features and must be assessed in your circumstances. Managed IT can handle agreed checks and updates, without confusing a feature's presence in RouterOS with an already secure or monitored configuration.
Can a router be changed remotely? Potentially, but an incorrect rule can disconnect administrator access. A recovery method and, where necessary, on-site assistance should be arranged.
Does a backup connection guarantee continuity? No. Failover needs testing with applications, tunnels and the return to the primary connection. Some sessions may need to reconnect, and affected users should understand that behaviour.
The current RouterOS documentation covers prerequisites, routing, filtering and VPNs. Its version should match the project. Examples provide a technical starting point to adapt and test before modifying a live network.
Review of your needs, comparison of options and clearly explained priorities.
Preparation, configuration, testing and coordination with the relevant providers.
Agreed support scope, documentation, licences and next steps.
A project? A question?
An initial conversation to understand your situation and decide on the next steps together.
Contact us
