Initially, I activated Hyper-V and downloaded the installation file. The setup process was straightforward but not entirely seamless. The installation itself took around fifteen minutes, but there was a hiccup during the assignment of IP addresses, particularly for WAN and LAN. OPNsense can function both as a production machine and an operating system, but for the latter, a server with two network cards is required—one for WAN and one for LAN.

I always handle the deployment myself in-house. 

I did the implementation of OPNsense in-house.

We took some help from our old industry connections, and systems integrators, and later our lab practices and tests started solving most of the issues.

I'm an integrator, so I mostly use OPNsense for VPN purposes and firewalls, and I use a couple of plugins for web blocking, and that's it. Only one person is required for deployment and maintenance; therefore, I handle all the deployment and maintenance.

I did not use a vendor to implement this solution, I did it myself.

We implemented OPNsense in-house.

We are implementors, and we provide this solution for our clients.

We handled the deployment on our own. 

The technical team required for deployment and maintenance purposes is small, probably around five people for every 100 devices.

It consist of a combination of managers, administrators and engineers.

I handled the implementation myself.

We deployed it ourselves. There was no need for a consultant for the deployment. We have two engineers for its deployment and maintenance.

I had some help internally from our network team when I was implementing the solution. However, I did not need outside assistance from a consultant or integrator.

We did the initial setup only by ourselves.

I did the implementation myself.