Well, there is a way to do that, but I assume you have to edit /boot/config/network.cfg for that.
What I do is the following:
IFNAME[0]="eth0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
DHCP_KEEPRESOLV="yes"
DNS_SERVER1="192.168.1.1"
USE_DHCP6[0]="no"
DHCP6_KEEPRESOLV="no"
DESCRIPTION[0,1]="eth0.1 - Data VLAN"
VLANID[0,1]="1"
PROTOCOL[0,1]="ipv4"
USE_DHCP[0,1]="yes"
DESCRIPTION[0,2]="eth0.10 - Data VLAN"
VLANID[0,2]="10"
PROTOCOL[0,2]="ipv4"
USE_DHCP[0,2]="no"
IPADDR[0,2]="192.168.10.11"
NETMASK[0,2]="255.255.255.0"
DESCRIPTION[0,3]="eth0.20 - Data VLAN"
VLANID[0,3]="20"
PROTOCOL[0,3]="ipv4"
DESCRIPTION[0,4]="eth0.4094 - Data VLAN"
VLANID[0,4]="4094"
PROTOCOL[0,4]="ipv4"
USE_DHCP[0,4]="no"
IPADDR[0,4]="192.168.255.11"
NETMASK[0,4]="255.255.255.0"
VLANS[0]="5"
SYSNICS="1"
However, this results in my date and time to run off after a while, unless I adapt and /etc/rc.d/rc.ntpd manually.
The line in the ntpd_start() procedure that defines what interface to use (ETH=eth0) is changed to: ETH=eth0.1.
This file however gets overwritten each time there is a reboot, so that's a bummer.
At least I hope this helps to some of us, as I don't like to see untagged traffic on a link that should behave as a trunk link.
I hope this helps at least to some of us hanging out in the fora here 🙂
Marc