Paolo Valerio <[email protected]> writes: > since a27d70a89 ("conntrack: add generic IP protocol support") all > the unrecognized IP protocols get handled using ct_proto_other ops > and are managed as L3 using 3 tuples. > > This patch stores L4 information for SCTP in the conn_key so that > multiple conn instances, instead of one with ports zeroed, will be > created when there are multiple SCTP connections between two hosts. > It also performs crc32c check when not offloaded, and adds SCTP to > pat_enabled. > > With this patch, given two SCTP association between two hosts, > tracking the connection will result in: > > sctp,orig=(src=10.1.1.2,dst=10.1.1.1,sport=55884,dport=5201),reply=(src=10.1.1.1,dst=10.1.1.2,sport=5201,dport=12345),zone=1 > sctp,orig=(src=10.1.1.2,dst=10.1.1.1,sport=59874,dport=5202),reply=(src=10.1.1.1,dst=10.1.1.2,sport=5202,dport=12346),zone=1 > > instead of: > > sctp,orig=(src=10.1.1.2,dst=10.1.1.1,sport=0,dport=0),reply=(src=10.1.1.1,dst=10.1.1.2,sport=0,dport=0),zone=1 > > Signed-off-by: Paolo Valerio <[email protected]> > ---
Thanks for this work - I think it looks good. Perhaps it should have a NEWS item mentioned that the userspace conntrack now supports matching SCTP l4 data. If you do spin a v4 with that change, you can keep my: Acked-by: Aaron Conole <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
