Open jesson1 opened 1 month ago
Your entries should expire after 10 seconds, not sure why they are not. However, as you are using a rather old/unsupported version of OVS, I would suggest upgrading first before trying to debug the issue.
We may not be able to upgrade the OVS version. Could someone provide some troubleshooting ideas?
The revalidator threads are responsible for cleaning up the flow table. You should first check the ovs-vswitchd log for any odd messages. If that does not show anything odd, I would set the log level for ofproto_dpif_upcall
to debug and see if anything pops up.
If this does not show anything, I would find a way to upgrade the OVS version.
Environment and version
Problem symptoms
ARP packets enter the OVS bridge through the tunnel and match the flow table:
![image](https://github.com/openvswitch/ovs-issues/assets/26702832/e4e7d270-a88b-4c43-83d9-08583936f8ee)
This is very strange. Upon inspecting the datapath, I discovered that the actual forwarding port is 1795, not the port expected by the OpenFlow.:
To verify, I captured packets on the virtual machine network interface corresponding to port 1795, and indeed, I captured the ARP packet:
In my observation, it seems that the OpenFlow flow table was not pushed to the datapath, and the datapath continues to use the old rules.
But the n_packets for this flow table entry remains 0, and the ARP packets are not captured on the virtual machine network interfaces corresponding to 1799 and 1800. I can ensure that the ARP packets indeed enter through the tunnel port, as I can capture and observe them:
My Question
Thank you for taking the time to read and consider this issue. Your help and support are greatly appreciated!