I would rate the initial setup as seven out of ten because sometimes we are facing issues, particularly with IP addressing. It takes a couple of hours to navigate and make the necessary preparations. Given that OPNsense is open-source, there isn't official support available at the moment, which adds an extra layer of complexity to issue resolution.

The deployment process takes almost an hour. The installation process involves several steps. First, you need to install the software. Then, configure the interfaces as needed. After that, establish the necessary rules for the software to function correctly. Finally, configure the VPN settings to ensure secure communication. I rate the solution a seven out of ten. 

The initial setup is very easy. In terms of configuration, you should have a design on hand. The system will only assess whatever you tell it to. For us, it is easy as we use a dedicated server for it. Right now, we're using a virtual machine. What we do is download and install, and that's it.

If you have everything in place, it might only take about three or four hours to deploy it. That's plenty of time to get the job done. Usually, one or two people handle the deployment process.

It is not so difficult to set up. You need to know the minimum things. I do it myself, and I am not an IT person. It is not my job.

The initial setup is straightforward. Being an engineer myself, I have no issues with systems on networks. The installation took around two hours to complete. When you download a system, it takes time. I’ve also installed one package named Zenarmor.

It is easy to set up, and the deployment took about six months.

The initial setup of OPNsense is straightforward. It took us a while to deploy the solution.

I rate the initial setup of OPNsense a nine out often.

The initial setup was straightforward for me. It took me approximately two days to set up the system initially. Subsequently, I began testing by progressively increasing the number of connections, deploying it through the unified features, and carefully monitoring specific ports while observing how it handles DHCP releases, IPs, and overall traffic. This process extended over about a week.

To begin the initial setup, you need to search for and download the ISO to initiate the process, followed by a two-step procedure. Afterwards, you proceed with command-line configurations, including setting up IP addresses. Once this initial phase is complete, navigation through the graphical user interface (GUI) becomes more straightforward. However, certain commands and configurations may still pose challenges. I rate it a seven out of ten.

The initial setup is very easy. The installation just takes minutes, but setting up everything may take a couple of hours.

A few years back when we first began using it, we were unable to find a proper document detailing different network scenarios for IP allocations for 2NIC cards. We went through aggressive discussion, reading blogs, and setting-up labs we started getting the knack for all possible configurable elements and started running several tests, packet forwarding, bombarding networks in the most ethical way possible, and verifying results. e.g. We created two separate networks, with WAN and LAN networks assigned to different classes. The menu-driven setup process is relatively easy, but you must know which IP address to define in the router, WAN section, and LAN sections. If this is clearly explained, the basic and fundamental aspects of your network will be in place, allowing you to set it up quickly.

Then we recommend clients purchase easily available commodity hardware-based motherboards with two NIC/Ethernet cards built-in, it simplified our tasks and so on.

OPNsense deploys it on the Azure marketplace. So, you can download it directly via the Azure marketplace. You do not have to be a partner. From our perspective, it's easy to configure and it's intuitive. We have a background with a lot of firewalls, and we were just looking for a small one.

We found that not many people have used it on Azure. The firewall itself is not bad, but the support around Azure in terms of documentation and the required infrastructure is not so good, but because we are Azure specialists, we found a very good solution. We would not recommend it for a beginner in Azure.

In terms of the implementation strategy, there is a cloud adaptation framework. There is a white paper from Microsoft containing best practices for deploying firewalls on Azure, and we had to provide a setup for this, which took some time because it was not easy. It took at least two weeks, but it was only a one-time job. After that, for each firewall, you only have to adapt the rules, which takes two days, but it also depends on the complexity of the infrastructure. If a customer has hundreds of endpoints, it takes longer for sure.

The initial setup is pretty straightforward. The deployment process took three to four hours. When I install OPNsense on the premises, I usually allow everything; after that, I go to one location. I work remotely on that firewall or VPN, so the first step is to put it online and remotely access the VPN server or firewall there. After that, I installed and configured it while working remotely.

The initial setup was straightforward and easy.

It took 30 to 45 minutes to set up and deploy OPNsense.

I believe the setup phase was a fusion of straightforwardness and complexity. It's not complicated, so it's fine.

It's deployed on-premises because we put it on our server, and it is hosted in Germany.

The deployment took approximately two hours.

I rate the initial setup of OPNsense a seven out of ten.

The initial setup is straightforward. The deployment took a couple of minutes. 

The initial setup was easy. 

The initial setup was easy. There are no issues with performance.

The setup was straightforward and the only mistake you can make is not to log in at the installer during the setup. I made this mistake once and configured a lot of features. After doing this I could not save the configurations on a disc. Generally, it was quite easy to install and to configure. 

The initial deployment took about two hours but figuring out how it works in detail and to run a roundabout took two or three days. 

Setting up OPNsense was easy for me. Even if you don't have experience, there is so much data available that you can follow so that the setup can be done easily.

The initial setup for OPNsense is an eight out of ten, especially if you know what you want to do and achieve from the solution. You also must try blocking methods based on what and how you want to block.

It took me two weeks to implement OPNsense completely. I set up the network and made a lab before using OPNsense in a production environment.

The initial setup is straightforward. It's an easy process.

It takes one hour to deploy.

We provide maintenance for our clients at a cost, however, 90% of our clients are familiar with the product and able to maintain the solution themselves.

The initial setup is straightforward. It's not overly complex or difficult. 

Our initial setup was more on the straightforward side.

It did not take a long time, although this can hinge on what needs to be accomplished. 

The initial setup is easy. It only takes 15-30 minutes to deploy.

The initial setup is straightforward and quite simplified. I work in a Linux environment so for me, it will be a bit easier.

The initial setup was straightforward. I also have experience with BSD services, so I had no issues at all. It took us half an hour to deploy it for 250 users.

The solution wasn't too complex, but the VPN setup isn't so reliable. It sometimes misbehaves or malfunctions or breaks down automatically. Occasionally it disconnects and you can't transfer the data from it.

Deployment took about a day or so. It takes maybe five or six hours to get everything up and running.

Since it's a simple firewall, anyone who has basic firewall knowledge can run and maintain it.

The initial set up was very easy. We had it working in one week or so. It was pretty fast.

The initial setup was easy. Deployment took about one day, maybe two. I do the deployment and handle the maintenance myself, so you only need one person to manage it.

It's quite easy to install and configure the rules.

The installation was straightforward.

The initial setup is very easy. It took around one hour. It's only getting the licensing and getting started. 

The initial setup of OPNsense is very easy.

I rate the initial setup of OPNsense a four out of five.

The initial set up was pretty easy. The total time for deployment took just one or two days.