[ovs-discuss] [OVS] bridges with vlan trunk and one interface

Scott Lowe scott.lowe at scottlowe.org
Mon Mar 28 16:59:22 UTC 2016


Please see my response below.


> On Mar 28, 2016, at 10:41 AM, LACROIX Jean Marc <jeanmarc.lacroix at free.fr> wrote:
> 
>>> How can i  bind eth-12-trus to eth0  in order to emulate old 802.1Q Linux eth0.12 interface ?
>> 
>> 
>> If you want multiple bridges, then don't add eth0 to the bridge; instead, add the VLAN sub-interface (eth0.9 or eth0.12) to each VLAN-specific bridge.
>> 
>> If you don't want to deal with VLAN sub-interfaces, then use a single bridge with eth0 and then tag your eth-11-wifi/eth-12-trus interfaces. You may need to adjust the native VLAN/untagged VLAN behavior, depending on your upstream switch.
>> 
> 
> admlocal at syspeo:~$ sudo ovs-vsctl show
> 25f2d62b-88b1-4315-9bad-ae8c8aaa9cd4
>    Bridge br-net-trusted
>        Port "eth-12-trus"
>            tag: 12
>            Interface "eth-12-trus"
>                type: internal
>        Port br-net-trusted
>            Interface br-net-trusted
>                type: internal
>    ovs_version: "2.3.0"
> 
> admlocal at syspeo:~$ sudo ovs-vsctl add-port br-net-trusted eth0.12
> ovs-vsctl: Error detected while setting up 'eth0.12'.  See ovs-vswitchd log for details.
> 
> Problem is that the bridge is changed event with error ?
> 
> admlocal at syspeo:~$ sudo ovs-vsctl show
> 25f2d62b-88b1-4315-9bad-ae8c8aaa9cd4
>    Bridge br-net-trusted
>        Port "eth0.12"
>            Interface "eth0.12"
>        Port "eth-12-trus"
>            tag: 12
>            Interface "eth-12-trus"
>                type: internal
>        Port br-net-trusted
>            Interface br-net-trusted
>                type: internal
> 
> 
> and in /var/log/openvswitch/ovs-vswitchd.log
> 
> 2016-03-28T16:53:54.708Z|00100|connmgr|INFO|br-net-wifi: added service controller "punix:/var/run/openvswitch/br-net-wifi.mgmt"
> 2016-03-28T16:53:54.736Z|00101|bridge|WARN|could not open network device eth0.11 (No such device)


You'll need to manually define the VLAN sub-interfaces (eth0.11, eth0.12, etc.) before you can add them to OVS. You can do this via ip commands (ip link add..., ip link set, etc.) or via configuration files (whatever your distribution uses).

-- 
Scott




More information about the discuss mailing list