tlabs.ru
> Cc: dev@dpdk.org
> Subject: Re: [RFC PATCH] ethdev: introduce NAT64 action
>
> External email: Use caution opening links or attachments
>
>
> On 9/21/2023 4:45 PM, Ferruh Yigit wrote:
> > On 9/19/2023 11:05 AM, Ori Kam wrote:
> >> Hi Bing
>
On 9/21/2023 4:45 PM, Ferruh Yigit wrote:
> On 9/19/2023 11:05 AM, Ori Kam wrote:
>> Hi Bing
>>
>>> -Original Message-
>>> From: Bing Zhao
>>> Sent: Friday, August 11, 2023 5:07 PM
>>> Subject: [RFC PATCH] ethdev: introduce NAT64 a
On 9/19/2023 11:05 AM, Ori Kam wrote:
> Hi Bing
>
>> -Original Message-
>> From: Bing Zhao
>> Sent: Friday, August 11, 2023 5:07 PM
>> Subject: [RFC PATCH] ethdev: introduce NAT64 action
>>
>> In order to support the communication between IPv4 a
Hi Bing
> -Original Message-
> From: Bing Zhao
> Sent: Friday, August 11, 2023 5:07 PM
> Subject: [RFC PATCH] ethdev: introduce NAT64 action
>
> In order to support the communication between IPv4 and IPv6 nodes in
> the network, different technologies are u
In order to support the communication between IPv4 and IPv6 nodes in
the network, different technologies are used, like dual-stacks,
tunneling and NAT64. In some IPv4-only clients, it is hard to deploy
new software and hardware to support IPv6.
NAT64 is a choice and it will also reduce the unneces
5 matches
Mail list logo