[ovs-dev] Q on weird OvS+conntrack behavior

Ravi Kerur rkerur at gmail.com
Fri Mar 26 00:53:17 UTC 2021


Hello,

I am working on OvS-DPDK and conntrack and seeing weird behavior, maybe I
am doing something wrong.

ovs-vswitchd --version
ovs-vswitchd (Open vSwitch) 2.13.3
DPDK 19.11.5

I have setup using
https://docs.openvswitch.org/en/latest/tutorials/ovs-conntrack/

After initial syn/syn-ack/ack, flow state moves established state


*root#ovs-appctl dpctl/dump-conntrack | grep
192.168.0.2tcp,orig=(src=192.168.0.2,dst=10.0.0.2,sport=1024,dport=2048),reply=(src=10.0.0.2,dst=192.168.0.2,sport=2048,dport=1024),protoinfo=(state=SYN_SENT)*


*root# ovs-appctl dpctl/dump-conntrack | grep
192.168.0.2tcp,orig=(src=192.168.0.2,dst=10.0.0.2,sport=1024,dport=2048),reply=(src=10.0.0.2,dst=192.168.0.2,sport=2048,dport=1024),protoinfo=(state=ESTABLISHED)*

Then I restart OvS, I still see conntrack entry still present so I wanted
to know where conntrack entries are stored (note that connection has not
received fin/fin-ack yet and restart happened before that). Second
question, is there a way (an API?) to extract flows from conntrack and
program OF tables?

r











*oot#ovs-ctl stop * Exiting ovs-vswitchd (24167) * Exiting ovsdb-server
(24146)root#ovs-ctl start * Starting ovsdb-server * system ID not
configured, please use --system-id * Configuring Open vSwitch system IDs *
Starting ovs-vswitchd * Enabling remote OVSDB managersroot# root#
ovs-appctl dpctl/dump-conntrack | grep
192.168.0.2tcp,orig=(src=192.168.0.2,dst=10.0.0.2,sport=1024,dport=2048),reply=(src=10.0.0.2,dst=192.168.0.2,sport=2048,dport=1024),protoinfo=(state=ESTABLISHED)*

Thanks,
Ravi


More information about the dev mailing list