Category: Ubiquiti

As an MSP I am always looking for improvements for our clients and as well as for our company. Therefore testing new devices and technologies is a daily part of my work.

Since nearly a decade I have been using Synology (or former QNAP) NAS systems as primary backup storage at my clients, as well as inside the company. They have nearly replaced all tape libraries (in fact I have only two remaining customers who are using a tape library).
I am are also very happy with our Synolgy NAS, they are typically no brainers, set and forget devices until a hard disc has to be replaced, very reliable and solid.

But however times moves on and Synology on the one hand did some things in the last years that gained my attention, e.g. vendor lock in for HDD, and on the other hand, the newer Synology NAS are very often over capable for the intended use to provide space for backups and replicate it to another site. For backup tasks I do not need additional software like Synology Drive, or Synology Photo which requires better hardware. On the other hand as an MSP, a central overview about the state of each backup NAS is a must have and even Synology insight exists, I never became really warm with it, some important information are missing, others which are less important for the workload a displayed very prominent. Therefore I am very interested in testing alternatives.

Since the beginning of my company we heavily used Ubiquiti devices, at the beginning mainly the Access Points, then continuing with the switches and since 3 to 4 years we have been using UniFi Protect and UniFi Access. I like the products, the quality and also the central management for MSPs which is one of the best currently available, in my opinion. Therefore I was very excited when they announced their NAS lineup. Even at the beginning it already looked as a good alternative for our current solution. But I decided to wait a little bit until some features are handed in later, which are quite important for the workload I want to test. With version 4 of the UNAS OS it was time to test it.

Therefor I purchased one UNAS2 for testing, my requirements are very clear and very common for a MSP:

• Easy and simple deployment even in large scale.
• Central Management which really gives me a compact overview over the most important data.
• Replication of the NAS to another site (in my case to an S3 storage).
• Integration into LDAP, AD or Azure.
• Support of NFS and Samba.
• Encryption for certain customers.

Deployment in large scale

Like all other UniFi products, this is something Ubiquiti knows how to handle, like nearly none of their competitors.

You plug in the device (you only need one network cable, the NAS is also powered by PoE) and after a short booting time the small display tells you the IP-Adress for further configuration.

Even better, if you have a UniFi-Network, then you have only to open the site manager and the NAS is shown and ready to adopt. Simply press the adopt button and after two or three minutes the device is ready to serve.

The device is shown as own site in the UniFi-Cloud and as a device in your UniFi-Network, like your Switches, AP and telephones.

The way the NAS is integrated into the UniFi ecosystem is very handy and clearly arranged.

Central Management

As already mentioned the UNAS can be managed using the UniFi-Cloud where ist is shown as an own site which can be a little bit confusing, especially if you are also using a UniFi-Gateway which is also managed using the cloud because it is not shown hierarchically.
On the other hand, the UNAS is running independently from any other UniFi device it can only be added to the whole ecosystem If the user wants it. Therefore this might be the right decision. The NAS also supports fabrics which helps to organize a large scale of UniFi devices and gateways.

The UniFi NAS series have an own tab in the Unifi-Cloud, called „Data Protection“ where you get the most important information about all of your UniFi NAS systems:

• State of each NAS
• Health Monitor of each NAS
• Backup Task

Especially the last bullet point makes the UNAS series already better for an MSP than a lot of the other manufacturers. There you have a unified view for all backup tasks which are configured and about their state. You can switch between the backup of your NAS and the backup state of any cloud backups of this NAS, even for M365.

Summarized, the UNAS series already has a better „Single Pane of Glass“ than Synology, or QNAP. Especially in combination with the other components of the UniFi ecosystem it’s something an MSP wants and is searching for.

Replication/Backup features

I would say this is currently the most weak discipline of the UNAS series.

Currently it only supports three backup methods:

Off-Site Backup allows the user to backup the complete NAS or parts of the NAS to a Remote NAS, to a CIFS/SMB-Server or to a cloud service. In the first glance this sounds solid, but in detail it shows a lack of important features:

1. Currently you can only recover a whole backup, from scratch. You have to reset the NAS, during the installation assistant you can choose from a backup. There is no possibility in the current UI to select e.g. a certain file to restore. I know that the UNAS supports snapshots, but recovering certain files from a backup without a complete reset of the UNAS is a basic need.
2. As a destination for a cloud backup you currently have only the options to backup to Google Drive, OneDrive, Dropbox, Amazon S3, Wasabi and Backblaze B2. There is no possibility to define a custom s3 provider. For me as an MSP this is simple not enough, we use European S3 providers because of legal terms and therefore we would need to define custom S3 providers.
3. There is no possibility to encrypt the data locally before sending it to the external backup destination.
4. It is also not possible to set a max data rate for uploading to the cloud. This must be done on the firewall/router.

Local backup supports backup to an external NAS using Rsync to the UNAS2, or creating a copy of the local console to another Ubiquiti NAS in the network. As already mentioned in the Offsite-Backup, the UI currently does not support any kind of restore tasks.

Cloud-Backup: Using the Cloud-Backup you can backup your M365 One Drive to the NAS, the support for Exchange, Teams and Sharepoint should follow soon. If this feature arrives, I probably will make my own test.

Generell spoken, the current backup feature of the UNAS series is very, very rudimentary, nor comparable with the features of Synology, QNAP or UNAS. I hope the next releases will improve this functionality.

Integration into LDAP, AD or Azure

The integration of the UNAS into an Active Directory works quite well, in the first try I had certain problems but all of them were solved with an update in August 2026. The integration is very easy, the device is added as a domain member and then synchronizes the AD users. Now you can directly access the NAS from any computer in the network. If the computer is a member of the domain and you have enough rights you can directly access the storage, otherwise you have to enter your domain credentials.
It also works fabulously with Apple, or Linux devices. There I have nothing to complain.

You can also use your credentials to access the web file browser of the UNAS and it works seamlessly with your Ubiquiti identity app and access your files on the NAS. There is also a possibility to use the NAS as a backup destination for your iOs (!) photo library. I did not test this.

Support of NFS and Samba

The UNAS series supports NFS and Samba and both protocols work really well and the whole NAS is very fast with its 2.5 Gbit port. Especially for this stock price the speed is really great!

I did three test:
First I added it using Samba to my Windows PC and put a copy of an old Windows Server VM on the NAS and started it from there, using VmWare Workspace.

In a second test I used the UNAS as a SR destination for VM on my XPC-NG cluster and ran two virtual machines, one windows server and one Ubuntu server parallel. It worked quite well, even though I did not use SSD drives. I would not run any heavy vm load on this NAS, but as already mentioned for this price the performance is more than well.

As a third test I used it as a backup destination, again for my XPC-NG cluster, and also in this role the UNAS2 made a really good job. On backup and restore operations the NAS always used nearly the maximum of its 2.5 Gbit connection to transfer data. There were only a few and small drops in the read and write statistics, even when backing up big VMs.

Conclusion

The UNAS2 is a very solid and good value NAS for anyone who is focused on a device which is very good in one thing: To store and provide files in a network. It has no advanced features like Docker, VMs, or applications like Synology Drive oder Synology Photo. It is a quite basic NAS with a fast network connection (a lot of more expensive NAS still have only a 1 Gbit network interface), with a really good value.

For an MSP who is already using Ubiquiti devices the UniFi NAS series is a good choice if they need a device which can be centralized accessed and managed and its main task is to store and provide data.
In the current state I will use the UNAS2 as a backup NAS for small clients which have virtualized environments and no problems with storing their external backup on AWS S3.

But I hope that Ubiquiti will soon improve and extends the features of the UniFi NAS series, especially a restore assistant in the UI for partly restore operations is a must have!

In this blog entry I will describe how to configure the U5G Max on a different WAN-Port than the default one, considering advanced feature like port forwarding.

I am using the following setup:

• One UDR7 as my home router.
• One U5G-Max Outdoor, with inserted sim card.
• I want to use Port 1 on my UDR7 for the U5G-Max because this port supports PoE.
• The U5G-Max Outdoor is already connected to Port 1 but not adopted.
• I have local access to the cloud gateway.

Changing the default WAN interface to Port 1

In the first step we need to change the default port for WAN1 to Port 1 of the UDR7 (this is also the most important step):

1. Go to “Settings” -> “Internet”, you will see the following settings:
   
   
2. Assign “Port 1” to “WAN1” and change “Port 4”, which is the default port for WAN to “Unassigned”:
   
   
3. Press “Apply changes” to store the changes.

In the next step we will adopt the U5G-Max.

Adopt the U5G-Max

To adopt the U5G-Max we go to “UniFi-Devices” and press “Click to Adopt” on the U5G-Max which should be shown:

After a certain time the small dot in front of the device switches to green and now we can check if the port forwarding rules are configured correctly.

Checking the port forwarding rules

1. We go to “Settings” and select the small icon to display the “Policy Table”.
2. Next we select “Port Forwarding” as Policy Type and select the policy rule.
3. The configuration will open, and there we need to check if the right WAN Interface is selected.
4. In our case this must be WAN1.
5. Finally we can check if the right ports are selcted and press “Apply” if we made any changes.

Now the port forwarding from the Internet using the U5G-Max should work.

Optional: Change the APN settings to static IP (A1):

Finally I will change the APN settings to a static IP-Address. This step refers to any customers of the Austrian provider A1 Telekom Austria like me, if you have a business tarif for your 5G Internet and therefore a static IP-address.

1. We go again to “UniFi Devices” and select the “U5G-Max”.
2. We go to “Settings” and scroll down until we can select “Use custom APN”.
3. Then we change the “APN Address” to fixip.a1.net
4. As “Authentication Type” we select “NONE”. All other settings remain as default.
   
5. With “Apply Changes” we submit the changes and after a short time the small dot in front of the devices switches again from orange to green.
6. As last step we need to restart the U5G-Max that the fix IP-address is applied. We switch to “Ports”, select “Port 1” and than we press “Power Cycle” which disables for a short time the power supply of the network port. Afterwards the U5G will restart and apply the fix IP-address.

I hope this step by step guide is helpful and feel free to comment.

After the change to winter time there were several burglaries in my area, therefore I decided, it is time to install a video surveillance.

This blog will lead you through my process and its integration into my ecosystem at home. It’s more a detailed plan how to realize it and not a step by step guide how to e.g integrate the camera feed into Homekit.

About the place:

I am living very close to the forrest with a small garden which cannot be seen very good from the other apparamtents. Because the garden and my terrace is long but narrow and can only be accessed when walking a narrow path.

For monitoring my garden I decided to use the Ubiquiti G4 Instance . Even the camera is very small and also cheap, it is a very good camera, with a good night view and AI regognization of persons, animals and movements. The camera connects via WiFi with my system an is powered using USB-C.

I do not want to waste space in my apartment with a lot of IT-stuff, for this I have my company. Therefore my whole IT/Network equipment at home consists of a Synology NAS, a UniFi Dream Machine for network and WLAN and a Hue Bridge for some of my lights in the apartment. All this equipment is located in a small shelve which does not need a lot of space. Therefore I want a single machine which provides Internet access, WiFI and as additional feature a recorder for my camera feed and should be accessible on my smartphone from everywhere. Until today this task is fulfilled by the Dream Machine (UDM). Unfortunatley the Dream Maschine does not support cameras, therefore I replaced it by the successor the Dream Router 7. This device looks like a white hat and supports Internet Access, WLAN and the different UniFi Apps like Network, Protect and Access. It has a slot to expand the internal storage. As additional feature this device has one PoE port which is very nice to use it, as power for my Hue bridge which does not support PoE natively, but there are a lot of adapters available. After making a backup of my UDM I switched it off and replace it by the Dream Router. After importing the backup I additionally installed Unifi Protect and plugged in my G4. The camera is immediately detected by the protect app and few minutes later the whole system is online and everything is ready. It’s really as simple as this!

With these two components I will do the following security deployment:

1. The camera will be mounted on the terrace at a position where it is nearly impossible to destroy it before the person can be recognized.
2. The Dream Router 7 will record the camera feed for a specifique time.
3. AI recognization is enabled and will detect a person if he/she enters the garden.
4. Unifi Protect is connected using Homebridge (which is installed on my Synology NAS) with Apple Homekit. See this video which explains how easy it is.
5. Now I directly integrate the camera feed into the dashboard of Apple Homekit.
6. Apple Homekit is already configured to notice if someone is at home.
7. Next I switch into the settings of my home and select camera & doors.
8. Inside I select the camera on the terrace an enable notifications with the following settings:
   • Time: Any
   • Persons: If no-one is at home
   • A certain movements is detected
   • A person is detected
   • Enable snapshots in the notification.

Now I will get a notification with a snapshot if a person enters the garden & terrace and no-one is at home.

With using automations you can configure additional actions for different situations which can be helpful to secure your home.

This is my basic security setup which works quite well.

With UniFi Protect 5.0 Ubiquiti integrated the support of cameras from third party manufactures. In this blog entry we will integrate a Reolink PTZ camera into UniFi Protect.

Requirements:

• Ubiquiti console with installed Protect with at least version 5, in my case I already have 5.1.87.
• A third party camera in the same subnet as the UniFi console.

Preparation:

Connect the camera with your network switch and be ensure that the camera has a valid IP-address and is in the same subnet as the console. If this is not possible, it does not really matters if you know the IP-address.

When using a Reolink it is necessary to enable RTSP on the camera, otherwise it will not work. To do this, access your camera using the IP-address and your username and password. After reset the reolink uses admin as username without any password.

After you have login, first change the password, Ubiquiti does not work with an empty password. To do this, login into the webinterface of your Reolink Camera go to “Device Settings” -> “System” -> “User Management” and press the “Change Password” button on the admin account.

Enter the current password and then two times the new password:

After you have entered a valid password, we now enable the ONVIF support on the Reolink device, because per default this is disabled.

Switch on the “Device Settings” page to “Network Settings” and open the “Advanced” tabsheet:

Now select “Set Up” under “Port Settings”. A dialog window is opened where you need to scroll down to the button until you find the toogles for RTSP and ONVIF, enable both:

You do not need to change the default ports. Press “Save” and now you are ready to adopt the camera into UniFi Protect.

Adopting into UniFi Protect:

1. Login to your UniFi Protect web application and go to “Settings” and enable the discovery support for Third-Party Cameras:

Press “Apply Changes” to store.

2. Now switch to “Unifi Devices”. If the Reolink camera is in the same subnet the camera will already be shown and is ready to get adopted:

2a. If the camera is in a different subnet or not shown press the question mark button right on the top. A window is opened where you press “try advanced adoption”:

Now enter the IP-Address, Username and Password of the camera and press “Confirm”:

2b. In this case this is not necessary, we can directly press “Click to Adopt”:

3. Enter the “Username” and “Password” and press “Confirm”:

After a short time the camera is adopted and ready to use:

As you can see in the following screenshot, Protect also supports “native” features of the camera, like the integrated PTZ or zoom function of this Reolink camera:

Removing the camera:

Removing the camera is as simple as with other Unifi devices:

1. Select the camera go to settings and press “Remove”:

2. When pressing “Remove” you have to choose what should happen with the recorded videos of the camera. In this case I decide that they should be deleted:

After pressing remove it will take a short time before the camera is successfully removed: