Am 02/10/16 um 13:54 schrieb Stuart Henderson:
>
> trunk is normally for interfaces which are completely interchangeable,
> i.e. configured identically from a layer-3 point of view (same
> subnets/vlans/etc).
>
> If it used to work with em0 being both a vlandev and a trunkport,
> that was probably a bug, I would expect it to be rejected the same
> way that configuring an IP address on a trunkport is rejected.
>
> For a normal wired-and-wireless setup with different subnets on each,
> you would normally just run dhclient on multiple interfaces.
>
Thanks for your explanation. Changing vlandev to trunk0 works:
vlan6: flags=208843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6>
mtu 1500
lladdr 3c:97:0e:ea:61:d1
priority: 0
vlan: 6 parent interface: trunk0
groups: vlan egress
status: active
inet6 fe80::3e97:eff:feea:61d1%vlan6 prefixlen 64 scopeid 0x9
inet6 2001:920:1846:1dc0:3e97:eff:feea:61d1 prefixlen 64
autoconf pltime 604797 vltime 2591997
inet6 2001:920:1846:1dc0:78a2:faf1:f165:8ef0 prefixlen 64
autoconf autoconfprivacy pltime 85969 vltime 604797
