Network firewall
Define required communications in OPNsense using readable rules and justified exceptions, then test authorised services before placing the firewall on an important network path that business users or hosted applications depend on.
OPNsense
OPNsense firewalls for SMEs in French-speaking Switzerland: prepare hardware, network rules, VPNs and ongoing maintenance with Sunitech to an agreed scope.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

OPNsense is a firewall and routing platform based on FreeBSD. It can organise internet access, separate networks and support private connections. For an SME in French-speaking Switzerland, the project should first describe permitted communications between teams, servers and specialist equipment. We define that scope with your responsible staff. The firewall controls traffic; it does not replace application permissions or computer protection.
Define required communications in OPNsense using readable rules and justified exceptions, then test authorised services before placing the firewall on an important network path that business users or hosted applications depend on.
Prepare OPNsense interfaces, networks and routes around the existing installation, checking hardware and dependencies so that users reach only the services included in the agreed scope and unintended paths are identified.
Organise separation between teams, visitors and devices in OPNsense, with explicitly permitted traffic and documentation of the business uses that justify communication between different areas of the network under your control.
Review VPN requirements in OPNsense against compatible functions and extensions, then define users, resources and access removal procedures without treating a remote connection as permission to reach every service on the network.
Retain a recoverable OPNsense configuration and the information needed to use it, then prepare a replacement procedure that accounts for interfaces, addressing and the business connections dependent on the firewall being restored.
Organise OPNsense version and extension reviews, useful event monitoring and maintenance windows, with tests that confirm essential communications after each planned change and responsibilities for investigating any unexpected effects on service.
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.
Choosing an appliance or virtualised installation depends on interfaces, traffic and availability requirements. VPNs and additional processing have their own demands. We check hardware compatibility, dependencies and the selected edition before deployment. An IT audit helps recover existing rules, networks and services. The plan should also establish how to administer or replace the firewall if its configuration becomes inaccessible.
We define interfaces, zones, filtering rules, address translation and necessary services. Administrator accounts are identified and configurations backed up. Any WireGuard connections are treated as part of the project, with access restricted to required resources. Before switchover, we prepare tests and recovery of the previous configuration. Checks also verify that unwanted access remains effectively blocked.
An open platform remains a system requiring maintenance. Updates, extensions and logs need follow-up within suitable windows. Features supplied by an extension or additional offering must be verified before being promised. Our cybersecurity support can include these arrangements within an agreed scope. Default settings do not represent your company's specific security policy and need examination.
Is OPNsense only a VPN? No. It is a firewall and routing platform that can integrate different VPN functions. Tunnels and access rules remain two separate configuration concerns.
Are two firewalls enough to guarantee availability? No. Providers, switches, power and failover conditions also need examination. Redundant architecture must be tested with the company's actual applications and connections.
The OPNsense manual covers sizing, rules, updates and VPN guides. Procedures should match the installed edition and version. We use them as a basis for documenting your configuration and the tests needed before it enters service.
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