| Message ID | 165694497267.33593.6714814733090986792.stgit@fed.void |
|---|---|
| State | Accepted |
| Commit | 5d875809a016cfa6491af7c7a12327208647ede9 |
| Headers | show |
| Series | [ovs-dev,v2] meta-flow: Document nw_proto limitation for IPv6 later frags. | expand |
| Context | Check | Description |
|---|---|---|
| ovsrobot/apply-robot | success | apply and check: success |
| ovsrobot/github-robot-_Build_and_Test | success | github build: passed |
| ovsrobot/intel-ovs-compilation | success | test: success |
On 7/4/22 16:29, Paolo Valerio wrote: > Signed-off-by: Paolo Valerio <pvalerio@redhat.com> > --- > lib/meta-flow.xml | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/lib/meta-flow.xml b/lib/meta-flow.xml > index 28865f88c..a1a20366d 100644 > --- a/lib/meta-flow.xml > +++ b/lib/meta-flow.xml > @@ -4101,6 +4101,15 @@ r r c c c. > opcodes greater than 255 are treated as 0; this works adequately > because in practice ARP and RARP only use opcodes 1 through 4. > </p> > + > + <p> > + In the case of fragmented traffic, a difference exists in the way > + the field acts for IPv4 and IPv6 later fragments. For IPv6 fragments > + with nonzero offset, <code>nw_proto</code> is set to the IPv6 protocol > + type for fragments (44). > + Conversely, for IPv4 later fragments, the field is set based on the > + protocol type present in the header. > + </p> > </field> > > <field id="MFF_IP_TTL" title="IPv4/v6 TTL/Hop Limit"> > Thanks! Applied. Best regards, Ilya Maximets.
diff --git a/lib/meta-flow.xml b/lib/meta-flow.xml index 28865f88c..a1a20366d 100644 --- a/lib/meta-flow.xml +++ b/lib/meta-flow.xml @@ -4101,6 +4101,15 @@ r r c c c. opcodes greater than 255 are treated as 0; this works adequately because in practice ARP and RARP only use opcodes 1 through 4. </p> + + <p> + In the case of fragmented traffic, a difference exists in the way + the field acts for IPv4 and IPv6 later fragments. For IPv6 fragments + with nonzero offset, <code>nw_proto</code> is set to the IPv6 protocol + type for fragments (44). + Conversely, for IPv4 later fragments, the field is set based on the + protocol type present in the header. + </p> </field> <field id="MFF_IP_TTL" title="IPv4/v6 TTL/Hop Limit">
Signed-off-by: Paolo Valerio <pvalerio@redhat.com> --- lib/meta-flow.xml | 9 +++++++++ 1 file changed, 9 insertions(+)