Maybe you want it to be an "internal" port:
ovs-vsctl set interface type=internal
On Thu, Jan 18, 2018 at 02:17:03PM +0100, Riccardo Ravaioli wrote:
> Hi Ben,
>
> I have a related question. I do the following in order to have a bridge br
> with ports 0.br, 1.br... and later add existing
In the example above my bridge name is br and my ports are named 0.br, 1.br,
etc.
It's just an example. I could have chosen myport0, myport1, etc.
On 18 January 2018 at 14:39, Shivaram Mysore
wrote:
> There is s typo in add-br command. Your bridge name is br instead
There is s typo in add-br command. Your bridge name is br instead of 0.br
/Shivaram
::Sent from my mobile device::
> On Jan 18, 2018, at 5:17 AM, Riccardo Ravaioli
> wrote:
>
> Hi Ben,
>
> I have a related question. I do the following in order to have a bridge
Hi Ben,
I have a related question. I do the following in order to have a bridge br
with ports 0.br, 1.br... and later add existing interfaces to such ports:
ovs-vsctl add-br br
ovs-vsctl add-port br 0.br
ovs-vsctl --id=@ifce create interface name=eth1 -- set port 0.br
interface=@ifce
When I
On Mon, Jan 15, 2018 at 09:50:52AM -0800, Fred Licht wrote:
>Is it possible to have an OVS port ‘name’ differ from the interface name?
>
> Bridge ovs-ha-sw
> Port ovs-ha-sw
> Interface ovs-ha-sw
> type: internal
> Port "bond1"
>
Hi,
Is it possible to have an OVS port ‘name’ differ from the interface name?
Bridge ovs-ha-sw
Port ovs-ha-sw
Interface ovs-ha-sw
type: internal
Port "bond1"
Interface "bond1"
To have the effect of:
Bridge ovs-ha-sw
Port