Sorry about the spam! I got an SMTP error through my OVN email and wasn't sure which email got out.
-----Original Message----- From: Ilya Maximets <i.maxim...@ovn.org> Sent: Tuesday, September 20, 2022 12:24 PM To: alinserd...@gmail.com; d...@openvswitch.org Cc: 'ldejing' <ldej...@vmware.com>; i.maxim...@ovn.org; 'ldejing' <svc.ovs-commun...@vmware.com> Subject: Re: [ovs-dev] [PATCH v2 1/1] datapath-windows: Alg support for ftp and tftp in conntrack On 9/20/22 09:12, alinserd...@gmail.com wrote: > Applied on master, thank you! Hi, Alin. Thanks for taking care of these! Though, I suppose, you didn't meant to reply to the same patch multiple times? :) Best regards, Ilya Maximets. > > -----Original Message----- > From: dev <ovs-dev-boun...@openvswitch.org> On Behalf Of ldejing via > dev > Sent: Friday, September 16, 2022 10:53 AM > To: d...@openvswitch.org > Cc: ldejing <ldej...@vmware.com> > Subject: [ovs-dev] [PATCH v2 1/1] datapath-windows: Alg support for > ftp and tftp in conntrack > > From: ldejing <ldej...@vmware.com> > > This patch mainly support alg field in ct action when process ftp/tftp > traffic. Tftp with alg mainly parse the tftp packet (IPv4/IPv6), > extract connect info from the tftp packet and create the related > connection. For ftp, previous version has supported process of ftp > traffic. However, previous version regard traffic from or to port 21 > as ftp traffic, this is incorrect in some scenario. This version adds > alg field in ct for ftp traffic, we could use ct(alg=ftp) to process > any ftp traffic from/to any port. > > IPv4/IPv6. > > Test cases: > 1) ftp ipv4/ipv6 use alg field in the normal and nat scenario. > 2) tftp ipv4/ipv6 use alg field in the normal and nat scenario. > > Signed-off-by: ldejing <ldej...@vmware.com> > --- _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
