Open yuntanghsu opened 1 year ago
The description mentions conntrack and iperf. Can you mention the OVS use case here?
65520 is the zone used by Antrea (in OVS flows). Only flows with zone 65520 miss some events here. I think maybe conntrack event is updated by OVS plays a role here?
@vlrpl any idea on this?
@yuntanghsu maybe you can post your question in ovs-dev or ovs-discuss as more people might see it.
When using conntrack -E to listen events for iperf3 traffic. Only one tcp update event (SYN_SENT) will be delivered. The other conntrack state change messages are not advertised.
I expect I can see the tcp state changes (SYN_SENT/SYN_RECV/ESTABLISHEDFIN_WAIT….etc) when I have a tcp connection. However, when I use iperf3 (iperf3 -c 10.244.2.9 -t 1) to have a tcp connection, I have following results:
In conntrack -E, there is only one tcp state (SYN_SENT). TIME_WAIT/CLOSE/CLOSE_WAIT is supposed to appear in events when a connection ends, but I can’t see any of them when using iperf3.
In conntrack -L, I can see the tcp state is changed to TIME_WAIT, which is supposed to be in conntrack events, but it isn’t.
If I use wget, I can see all the tcp states in events:
Here is a commit that fixed a similar issue.