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:


Mind the VLAN_ID=<vlan id> addition. Make sure ONBOOT is set to yes. And that’s it. Reboot DSM and the interfaces will be up & running and will even appear in the GUI. Needless to say, you will need your switch-side to be configured with a VLAN trunk containing the correct VLAN tags.

Happy tagging on your Synology running DSM6.0! 🙂

Comments (19)

  1. Hi Niels,

    thanks for sharing this information. It was the perfect solution for me. And if someone misconfigured the networt like me, no problem. Just resetting [1] the network and try again.

    Cheers, Steffen

  2. Thanks for sharing the information. It has helped me with configuring the RS3614xs. I was wondering if you setup VLANs on the devices and then setup High Availability? Do you know if there is a way to change the HA cluster settings to use VLANs also? Thanks

  3. Does anyone now if these manual config file changes persist through upgrades/updates? Or do they have to be reapplied after each update?

      1. Thanks. I’ll try to remember and report back after the next update.

        I setup a bonded connection in the Synology, set switch ports to trunk + LACP, and then followed the directions above. Had VLANs working correctly within 5 minutes – excellent guide!

        I’ll never understand why Synology doesn’t support VLAN out of the box. a 4 NIC bonded link with VLANs is often a much more efficient use of the connections than 4 separate links dedicated to individual VLANs/networks.

  4. Hi,

    Is someone using their Synology as a DHCP server.
    If yes, can the Synology DHCP server assign ip addresses to different Vlan’s?

    1. Hi Casper,

      I’m not using a Synology, but the multiple VLAN interfaces present themselves in the control panel > DHCP Server. That would mean that you should be able to create a DHCP per VLAN (interface). Hope this helps.

  5. I set this up and it worked for me, however now it shows 2 instances of Bond1 in the GUI. Do you know of a way to assign different names?

  6. Hi and thank you very much, this helped me a lot. But I have one big problem with DLNA. It seems, that the mediaserver isn’t using the default network interface. I cannot find my NAS using upnp or dlna as long I have more than oen network interface enabled. Did you have same troubles or is there any tweak at the mediaserver configuration?

  7. Hi. I’ve got another problem … we use a diskstation in a subnet ( I can access it fine from machines on that same subnet.
    But if I try from machines on different subnet (10.16.2.x) it does not work. The network is setup correctly (two routers with static route between) – everything else on the network works fine between the two subnets.
    I can’t ping the IP of the diskstation whereas any other IP works. I’m not sure if this solution with VLAN will help in my case? Any ideas?

    1. You may want to add the 10.16.2/24 subnet (and any other subnets you have in your network) to your routing table and a proper gateway to it.

  8. Hi! Thank you for the post. I have Open Virtual Switch and settings seem to change there, so I cannot set this up by just copying the contents above or the contents of my ifcfg-ovs_bond0 file and modifying it. What should a file meant for a bond device in VLAN3…say ifcfg-ovs_bond0.3 have?

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.