On Thu, Aug 16, 2018 at 12:39 AM, Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) <matfa...@cisco.com> wrote:
> Max_frag value is applied when fragments arrived out of order > Ahhh.... That wasn't clear... But I see... > (non-initial fragments arrive before first fragment which contains L4 > header), fragments are stored and waiting for first fragment (max_frag is > limit for number of stored fragments). Fragments are dropped in > nat44-in2out-reass or nat44-out2in-reass node. Whether fragments are > dropped depends on order. All fragments should be dropped when max_frag is > 1 and 2 non-initial fragments are received before first fragment. After a > brief look into the code I see that this is not current behaviour and > dropped is only second fragment so I think some improvements should be > done in the future. > Would you like a bug report to keep track of that? > Matus > jdl
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10206): https://lists.fd.io/g/vpp-dev/message/10206 Mute This Topic: https://lists.fd.io/mt/24529319/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
