On Thu, Aug 16, 2018 at 12:39 AM, Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco) 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),
so I think some improvements
should be done in the future.
Matus
From: Jon Loeliger
Sent: Wednesday, August 15, 2018 4:06 PM
To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)
Cc: vpp-dev
Subject: Re: [vpp-dev] NAT Fragment Reassembly
On Wed, Aug 15, 2018 at 8:50 AM, Jon
On Wed, Aug 15, 2018 at 8:50 AM, Jon Loeliger wrote:
> On Wed, Aug 15, 2018 at 12:49 AM, Matus Fabian -X (matfabia - PANTHEON
> TECHNOLOGIES at Cisco) wrote:
>
>> Hi Jon,
>>
>>
>>
>> NAT plugin does virtual fragment reassembly – it enables to translate
>> non-initial fragments without L4 header
On Wed, Aug 15, 2018 at 2:30 AM, Ole Troan wrote:
> Jon,
>
> Thanks for bringing this up. In addition to Matus’ answer.
>
Hi Ole,
Thanks!
> There is a distinction to be made between forwarding and terminating
> traffic.
> And there is a nice grey middle ground between the two.
>
> Some featur
On Wed, Aug 15, 2018 at 12:49 AM, Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco) wrote:
> Hi Jon,
>
>
>
> NAT plugin does virtual fragment reassembly – it enables to translate
> non-initial fragments without L4 header otherwise NAT is unable to gather
> port information from the non-
Jon,
Thanks for bringing this up. In addition to Matus’ answer.
There is a distinction to be made between forwarding and terminating traffic.
And there is a nice grey middle ground between the two.
Some features does forwarding on the transport header, like NAT, MAP-E, MAP-T
and so on, those do
@lists.fd.io On Behalf Of Jon Loeliger
Sent: Tuesday, August 14, 2018 11:53 PM
To: vpp-dev
Subject: [vpp-dev] NAT Fragment Reassembly
VPPeople,
A few months ago, the vppctl command 'set interface reassembly' was
added along with its API call, ip_reassembly_enable_disab
VPPeople,
A few months ago, the vppctl command 'set interface reassembly' was
added along with its API call, ip_reassembly_enable_disable (commit
4c53313cd7e9b866412ad3e04b2d91ac098c1398).
What is the relationship of this fragment reassembly and this
enable/disable flag WRT to the NAT's fragment
