Use case understanding for l3fwd

[Dinesh Kumar <raidinesh@utexas.edu>]

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

Hello Experts,

I am trying to run the following scenario using l3fwd example in
dpdk-stable-21.11.2 release .

The flow is :

         VM1
                                 VM2
ns0->tap0<IPV4 IP>->DPDK       <--------------------->  DPDK-> bind a
device  with IP <IPV4 IP >


The first question I have for VM2:
I assigned IP to the device and can see eth and static ip address via  'ip
add ', then after binding it to dpdk, I can not see this information via ip
add because it is not controlled by kernel module.
Is there any way to see ip and ethernet address after binding to DPDK?
Is this process correct to assign IP  and then device to DPDK?


on VM1:
 After starting the DPDK application, I can see a tap0 device created in
kernel mode via 'ip add show'.Then I attached this interface with network
namespace via:

ip netns add ns0
ip link set tap0 netns ns0
ip netns exec ns0 ip addr add <IPV4 Address> dev tap0
ip netns exec ns0 ip link set tap0 up
ip netns exec ns0 ip link set lo up

Still, I am not able to ping anything from this ns0.

Do I need any other configuration to ping via ns0 to VM2?

Sorry, in case I am asking any dumb questions, I am new to DPDK and trying
to make the use case work.
Any help/pointer is really appreciated.

[-- Attachment #2: Type: text/html, Size: 1587 bytes --]