On 6/29/21 6:04 PM, Paolo Valerio wrote:
> Dumitru Ceara writes:
>
>> On 6/25/21 2:01 PM, Paolo Valerio wrote:
>>> Dumitru Ceara writes:
>>>
On 6/21/21 12:06 PM, Paolo Valerio wrote:
> when a packet gets dnatted and then recirculated, it could be possible
> that it matches another
Dumitru Ceara writes:
> On 6/25/21 2:01 PM, Paolo Valerio wrote:
>> Dumitru Ceara writes:
>>
>>> On 6/21/21 12:06 PM, Paolo Valerio wrote:
when a packet gets dnatted and then recirculated, it could be possible
that it matches another rule that performs another nat action.
The
Dumitru Ceara writes:
> On 6/25/21 2:01 PM, Paolo Valerio wrote:
>> Dumitru Ceara writes:
>>
>>> On 6/21/21 12:06 PM, Paolo Valerio wrote:
when a packet gets dnatted and then recirculated, it could be possible
that it matches another rule that performs another nat action.
The
On 6/25/21 2:01 PM, Paolo Valerio wrote:
> Dumitru Ceara writes:
>
>> On 6/21/21 12:06 PM, Paolo Valerio wrote:
>>> when a packet gets dnatted and then recirculated, it could be possible
>>> that it matches another rule that performs another nat action.
>>> The kernel datapath handles this
Dumitru Ceara writes:
> On 6/21/21 12:06 PM, Paolo Valerio wrote:
>> when a packet gets dnatted and then recirculated, it could be possible
>> that it matches another rule that performs another nat action.
>> The kernel datapath handles this situation turning to a no-op the
>> second nat action,
On 6/21/21 12:06 PM, Paolo Valerio wrote:
> when a packet gets dnatted and then recirculated, it could be possible
> that it matches another rule that performs another nat action.
> The kernel datapath handles this situation turning to a no-op the
> second nat action, so natting only once the
when a packet gets dnatted and then recirculated, it could be possible
that it matches another rule that performs another nat action.
The kernel datapath handles this situation turning to a no-op the
second nat action, so natting only once the packet. In the userspace
datapath instead, when the
