Re: [ovs-discuss] change configuration of VLAN access port

2021-01-21 Thread Tonghao Zhang
On Thu, Jan 21, 2021 at 8:13 AM Matthias Waehlisch wrote: > > > ... i was able to change the configuration using "ovs-vsctl set port > xyz vlan_mode=native-untagged" but the virtual switch still sends > packets that include a vlan tag on the access port instead of removing > the tag. this is quite

Re: [ovs-discuss] cells v2 routing question

2021-01-21 Thread Pedro Sousa
Hi Numan, you're right, I upgraded to ussuri and now I see the commands, however in the second site, which is an openstack cell, I don't see the bd, I only see an ovn-controller and ovn-metadata running on compute nodes. My understanding is that BD is on the central site only, and cell is connect

Re: [ovs-discuss] change configuration of VLAN access port

2021-01-21 Thread Ben Pfaff
On Wed, Jan 20, 2021 at 05:25:49PM +0100, Matthias Waehlisch wrote: > Hi, > > i'm wondering how to change the VLAN setting of an access-port > without deleting the port. > > when i already added a port to a switch (ovs-vsctl add-port ...), and > and want to change the VLAN setting via "ovs-

[ovs-discuss] watch_group liveness check for OVS groups

2021-01-21 Thread Alexander Constantinescu
Hi, TL;DR: I am wondering if there's any specific action/convention that needs to be defined for groups which are referenced by a watch_group, as to have the liveness check correctly working? FYI: I can't use a liveness check on a dedicated OVS port in this case. I have not been able to find much

Re: [ovs-discuss] watch_group liveness check for OVS groups

2021-01-21 Thread Ben Pfaff
On Thu, Jan 21, 2021 at 08:20:16PM +0100, Alexander Constantinescu wrote: > Hi, > > TL;DR: I am wondering if there's any specific action/convention that needs > to be defined for groups which are referenced by a watch_group, as to have > the liveness check correctly working? FYI: I can't use a liv

Re: [ovs-discuss] watch_group liveness check for OVS groups

2021-01-21 Thread Ben Pfaff
On Thu, Jan 21, 2021 at 08:20:16PM +0100, Alexander Constantinescu wrote: > I have not been able to find much documentation surrounding watch_group, > the only doc I've been basing myself on is: > http://www.openvswitch.org/support/dist-docs/ovs-ofctl.8.html OVS follows the OpenFlow standard here,

Re: [ovs-discuss] ovs-ofctl broken when getting table features reply

2021-01-21 Thread Ben Pfaff
OK, I figured out the problem. Property 10, OFPTFPT_WILDCARDS, is missing. OF1.3 section 7.3.5.5.2 says that it's mandatory: "If a specific property does not have any capability (for example no Set-Field support), a property with an empty list must be included in the property list." I think that

Re: [ovs-discuss] ovs-ofctl broken when getting table features reply

2021-01-21 Thread Dickens Yeh
Thanks for helping me. I find the section in OF1.3.2 spec, and re-check with pcap file as you said. I think I was missed the important message: "table features message missing required property", but only focus on "received bad reply: (***only uses 512 bytes out of 7056***)". Thanks. best wishes

Re: [ovs-discuss] ovs-ofctl broken when getting table features reply

2021-01-21 Thread Ben Pfaff
Oh, I see. I'm glad I was able to help. On Fri, Jan 22, 2021 at 10:21:21AM +0800, Dickens Yeh wrote: > Thanks for helping me. > > I find the section in OF1.3.2 spec, and re-check with pcap file as you said. > I think I was missed the important message: "table features message missing > required