Synology DSM6.0 VLAN support

I’ve noticed some distress on the web because, with the release of Synology DSM version 6.0, it is no longer possible to use the vconfig command. This command was used to configure VLAN tagging on your interfaces.

It is however still perfectly possible to create multiple sub-interfaces on a physical interface or bond without using the vconfig command. All you need to do is create additional config-files for each of you sub-interfaces. Each sub-interface represents a VLAN ID. The config-files are found in /etc/sysconfig/network-scripts/.

Note: shell access is required to your Synology. So you should enable SSH for instance.

In the example below, you will see my Synology has a bond using eth0 and eth1. My setup required to have some additional VLAN tagged sub-interfaces on top of my physical bond interface.

As you can see, I have a sub-interface for VLAN 100, 120, 130 and 20. You only need to copy a config-file using the naming format ifcfg-<phy int>.<vlan-id>, and adjust it to your needs. A (copied) config-file looks like this:


Read More

Homelab Synology backup strategy

A while ago I finally had some attention for my much beloved data. I gave some thought on how my data would be safe if disaster would struck, like my Synology NAS catching fire. Or worse, my house…

So when I speak of  ‘my beloved data’, I am talking about:

  • Homelab data (VM’s etc.)
  • Personal documents
  • Photos & videos

I could live with my homelab data being lost. I would not be a happy man, but a complete homelab reinstall would be possible without any backup. However, if one can avoid the loss of data, one should. 🙂

More important however, are my personal documents and my photos/videos. Those are invaluable to me! I wanted to make sure that all this data is centralized on my Synology NAS and I have the requirement for an off-site backup. The off-site backup would have to be affordable while growing in GB’s. The RTO would not matter that much as long as I’m able to recover the data.
Also, I would like to reduce the number of cloud storage solutions (Google Drive, Onedrive, Dropbox) and their associated clients.

The diagram below shows the setup I came up with:



Read More