ovs-appctl ofproto/trace vmbr0 thinks the bridge name is missing...

linum

Renowned Member
Sep 25, 2011
99
3
73
I tried to debug an ARP issue and want to use the command
Code:
ovs-appctl ofproto/trace vmbr0
as described here. But the command failed with:

Code:
root@xxx:~# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 3.1.0
DB Schema 8.3.1
root@xxx:~# ovs-appctl ofproto/trace vmbr0
syntax error at vmbr0 (or the bridge name was omitted)
ovs-appctl: ovs-vswitchd: server returned an error

Anyone an idea what I'm doing wrong?

Code:
pveversion
pve-manager/8.0.3/bbf3993334bfa916 (running kernel: 6.2.16-3-pve)
 
Hi,

command ovs-appctl

Code:
# ovs-appctl list-commands|grep ofproto/trace

ofproto/trace  {[dp_name] odp_flow | bridge br_flow} [OPTIONS...] [-generate|packet]


needs two arguments.

Look at
https://docs.openvswitch.org/en/latest/topics/tracing/

where command

$ ovs-appctl ofproto/trace br0 in_port=3,tcp,nw_src=192.0.2.2,tcp_dst=22

is explain as

The first line is the trace command. The br0 is the bridge where the packet is going through.
The next arguments describe the packet itself. For instance, the nw_src matches with the IP source address.
All the packet fields are well documented in the ovs-fields(7) man-page

Vlodek
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!