On 09/21/2018 02:48 PM, Ben Pfaff wrote:
No. A port can be an internal port or a vxlan port. It can't be both.
Thank you for the confirmation.
Maybe you should use flows instead of OVSDB configuration. Flows can
also direct packets from one port to another. I guess that this would
be
On Tue, Sep 18, 2018 at 11:29:52AM -0600, Grant Taylor via discuss wrote:
> On 09/17/2018 10:29 PM, Ben Pfaff wrote:
> >Something like this? I have not tested it.
> >
> >ovs-vsctl add-port br0 port0 -- set interface port0 type=internal -- set
> >port port0 tag=100
> >ovs-vsctl add-port br0 port1
Hi Ben,
Thank you for the reply.
On 09/17/2018 10:29 PM, Ben Pfaff wrote:
Something like this? I have not tested it.
ovs-vsctl add-port br0 port0 -- set interface port0 type=internal -- set port
port0 tag=100
ovs-vsctl add-port br0 port1 -- set interface port1 type=internal -- set port
On Sat, Sep 15, 2018 at 07:40:11PM -0600, Grant Taylor via discuss wrote:
> What is the best way to map a specific flow ID coming in a VTEP to a
> specific internal port?
>
> # ovs-vsctl add-br br0
>
> # ovs-vsctl add-port br0 port0 -- set interface port0 type=internal -- set
> port port0
What is the best way to map a specific flow ID coming in a VTEP to a
specific internal port?
# ovs-vsctl add-br br0
# ovs-vsctl add-port br0 port0 -- set interface port0 type=internal --
set port port0 tag=100
# ovs-vsctl add-port br0 port1 -- set interface port1 type=internal --
set port
