Re: [ovs-dev] [PATCH v2] conntrack: add coverage counters for L3 bad checksum

2021-07-01 Thread Ilya Maximets
On 4/30/21 7:12 PM, Paolo Valerio wrote: > similarly to what already exists for L4, add conntrack_l3csum_err > and ipf_l3csum_err for L3. > > Received packets with L3 bad checksum will increase respectively > ipf_l3csum_err if they are fragments and conntrack_l3csum_err > otherwise. > > Although

Re: [ovs-dev] [PATCH v2] conntrack: add coverage counters for L3 bad checksum

2021-05-11 Thread Aaron Conole
Paolo Valerio writes: > similarly to what already exists for L4, add conntrack_l3csum_err > and ipf_l3csum_err for L3. > > Received packets with L3 bad checksum will increase respectively > ipf_l3csum_err if they are fragments and conntrack_l3csum_err > otherwise. > > Although the patch

Re: [ovs-dev] [PATCH v2] conntrack: add coverage counters for L3 bad checksum

2021-05-11 Thread Eelco Chaudron
On 30 Apr 2021, at 19:12, Paolo Valerio wrote: > similarly to what already exists for L4, add conntrack_l3csum_err > and ipf_l3csum_err for L3. > > Received packets with L3 bad checksum will increase respectively > ipf_l3csum_err if they are fragments and conntrack_l3csum_err > otherwise. > >

[ovs-dev] [PATCH v2] conntrack: add coverage counters for L3 bad checksum

2021-04-30 Thread Paolo Valerio
similarly to what already exists for L4, add conntrack_l3csum_err and ipf_l3csum_err for L3. Received packets with L3 bad checksum will increase respectively ipf_l3csum_err if they are fragments and conntrack_l3csum_err otherwise. Although the patch basically covers IPv4, the names are kept