On Wed, Jun 05, 2024 at 09:26:02PM +0800, Wilson Peng wrote: > Hi, Simon, > In this case, for tftp packet processing, it does have a child-parent > processing logic just like ftp in tcp. > Tftp packet1 from port1 to 69 and it will create one new conntrack entry > and create one related conntrack > entry also with src-port 0 and dst-port port1. Original idea is if the > tftp reply packet is from port2 to port1 and > then it will create one new conntrack entry then it could set this > conntrack entry(port2->port1) parent be equal > to conntrack_entry(port1-->69). > > In the processing part, if the tftp reply packet is from 69 to port1 > then it would hit the original conntrack entry > (port1-->69) and lead to conntrack_entry parent be equal to itself. > > Only ftp/tftp traffic processing will have parent-child logic.
Hi Wilson, Thanks for the explanation. I understand that this patch will prevent OVS from crashing (good!). But I'm unclear how flows that would have caused a crash will be handled by conntrack with this patch present. Could you shed some light on that too? _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
