tag:blogger.com,1999:blog-7036379482487192438.post1209706892248173832..comments2023-03-15T11:27:40.919+01:00Comments on the birdhouse in my soul: Multiple VLANs on a Synology NASBert de Bruijnhttp://www.blogger.com/profile/14859034314670252617noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-7036379482487192438.post-18290893852704614352014-03-10T22:33:28.459+01:002014-03-10T22:33:28.459+01:00This article has another approach (and links back ...This article has another approach (and links back here): http://www.ucguerrilla.com/2013/10/provisioning-synology-nas-to-support.htmlBert de Bruijnhttps://www.blogger.com/profile/14859034314670252617noreply@blogger.comtag:blogger.com,1999:blog-7036379482487192438.post-24335207495902454292013-09-17T06:54:15.781+02:002013-09-17T06:54:15.781+02:00I definitely can't take credit for it as I fou...I definitely can't take credit for it as I found it on another blog, but another way is to configure the bonding interface with two or more ports, assign a default VLAN ID such as 1 for 802.1q tagging. Once this is done, SSH in to the box and make clones of the /etc/sysconfig/network-scripts/ifcfg-bond0.1 file for each additional VLAN you want to support (changing the filename, DEVICE and VLAN_ID as appropriate). By assigning a 802.1Q tag to the default channel, DSM will automatically manage kernel modules.<br /><br />Using this method, DSM should bring up the VLAN interfaces automatically and even (at least in 4.3) exposes them via the GUI albeit with limitations. You can manage the IP addresses / MTU from the GUI for the additional VLAN interfaces as well and it will survive a reboot. I haven't tested with all other services, but I can say basic file sharing, NFS and iSCSI will also automatically start up on the cloned VLAN interfaces.Aaron Von Gausshttps://www.blogger.com/profile/17692348946134871817noreply@blogger.comtag:blogger.com,1999:blog-7036379482487192438.post-10704204708766341902013-09-17T06:51:37.009+02:002013-09-17T06:51:37.009+02:00This comment has been removed by the author.Aaron Von Gausshttps://www.blogger.com/profile/17692348946134871817noreply@blogger.comtag:blogger.com,1999:blog-7036379482487192438.post-70350429967456378682013-08-28T16:57:45.275+02:002013-08-28T16:57:45.275+02:00Admin doesn't have privileges from the command...Admin doesn't have privileges from the command line. Log in as root with the same password as admin.Anonymoushttps://www.blogger.com/profile/11003406465459192097noreply@blogger.comtag:blogger.com,1999:blog-7036379482487192438.post-90010264734151105332013-07-28T00:02:50.326+02:002013-07-28T00:02:50.326+02:00I have tried this but get "/lib/modules/8021q...I have tried this but get "/lib/modules/8021q.ko: Permission denied" although I am log in as admin. the other question I have will this code be resident after reboot or upgrade?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7036379482487192438.post-31953659340580283802013-01-06T16:12:01.151+01:002013-01-06T16:12:01.151+01:00An additional note: if you want to present iSCSI t...An additional note: if you want to present iSCSI targets on manually created VLAN interfaces, you have to add a line to the corresponding /etc/sysconfig/network-scripts/ifcfg-IF.VLAN file (e.g. ifcfg-bond0.15) specifying the IP address IPADDR=192.168.15.2 . If you don't do this, nothing will be listening on port 3260 on this interfaceBert de Bruijnhttps://www.blogger.com/profile/14859034314670252617noreply@blogger.com