From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 43E3A42935 for ; Thu, 13 Apr 2023 19:32:38 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ACE7941138; Thu, 13 Apr 2023 19:32:37 +0200 (CEST) Received: from mail-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) by mails.dpdk.org (Postfix) with ESMTP id 03EB7410F9 for ; Thu, 13 Apr 2023 19:32:36 +0200 (CEST) Received: by mail-ua1-f42.google.com with SMTP id ba16so10825966uab.4 for ; Thu, 13 Apr 2023 10:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=utexas-edu.20221208.gappssmtp.com; s=20221208; t=1681407156; x=1683999156; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Y7emKrHFG2v5ASlosZtQCVdIG6Y3E0zn0pyGiPue/vY=; b=olbn8CHUoToNPgHtbqTAw0DuSfVzNP/ZmkX2i3XLK1TCMZxeZYiP/PEt5yJEUQYGfK +dUaVIRoX3ZcbJIhZ6foNuBZvLB06co8fRJFBUSS14i+DtREMd2ruf7KGT8EuOzMSHCQ OxlToK4vZBVrGZGtDPIRRNeLB9hggM3qXdWfd1wQkjnMkWSuw0TP4gf8vWRlDcD+Q9OB pgFXepVm8ANBVLciF1C1bQ1kb1Sd5J3kxGUdAqMLgXoswmTejU27FA2hLdS/1HXTb98r svvWidm6iVR0W8b4dckkw74TsXrtLlc4x0v1b7OBdmL3byFYwBlgZdBuT8G/qgxM/6JE ZG2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681407156; x=1683999156; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Y7emKrHFG2v5ASlosZtQCVdIG6Y3E0zn0pyGiPue/vY=; b=f7M1z3KpuykLoVI5dojHkkpoMwp0OwDK7YfK7U72X51IH8YNRG2OdZiUovPqe5vxfU jtaB3sAy3jlLIujtYBR66NjBs+EY0BW0ZeRt0Ai4JDlNlta2EOvT+OSK2KGVv4H3cwCO WXXUciIL/3/rs8anxpYTI3SUJqe5Py0XAf+czy3b5oeNTbFTGfb57ttcdxb/XOwMWuUf nvCoDPLcSiqaZjpAq4ksLeIi3cyhhrRqDj0lmaHsEFfTx71WggroKbQA1RqMQI9jhLUl jAWrcaRV2qRUxXUbbuxjiI0AVnKflC9ylJlCbP7eeO6KMxEnIhinOwnvBzlNo9+uaU+r XQLw== X-Gm-Message-State: AAQBX9d8MT+RjXzrWQE0XcCzZthUjPy5Mtc6tBsabNJHO4mTpseRRAoi Z7wrSHBosqI1bFhkoX/L0uLxqCYUjKlpwjE/LopCT1DVsOalCwKcuVx2dw== X-Google-Smtp-Source: AKy350atWvFN0XKhU8JLch2BgPijIcDq/5dra5/+b1uCdYEhhJ/fszySOeYe5EzNGFuTO/4F0sFcK6b2Z5Zar50RvvE= X-Received: by 2002:ab0:5b07:0:b0:68b:94c5:7683 with SMTP id u7-20020ab05b07000000b0068b94c57683mr1535006uae.0.1681407156005; Thu, 13 Apr 2023 10:32:36 -0700 (PDT) MIME-Version: 1.0 From: Dinesh Kumar Date: Thu, 13 Apr 2023 13:32:25 -0400 Message-ID: Subject: Use case understanding for l3fwd To: users@dpdk.org Content-Type: multipart/alternative; boundary="00000000000041ccd405f93b1c1f" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --00000000000041ccd405f93b1c1f Content-Type: text/plain; charset="UTF-8" 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->DPDK <---------------------> DPDK-> bind a device with 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 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. --00000000000041ccd405f93b1c1f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Experts,

I am trying to run the following=C2= =A0scenario=C2=A0using l3fwd example in dpdk-stable-21.11.2 release .
The flow is :

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0VM1=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0VM2
ns0->tap0<= IPV4 IP>->DPDK=C2=A0 =C2=A0 =C2=A0 =C2=A0<--------------------->= ;=C2=A0 DPDK-> bind a device=C2=A0 with IP <IPV4 IP >


T= he first question I have for VM2:
I assigned IP to the device and can se= e eth and static ip address via=C2=A0 'ip add ', then after binding= it to dpdk, I can not see this information via ip add because it is not co= ntrolled=C2=A0by kernel=C2=A0module.
Is there any way to see ip and ethe= rnet address after binding to DPDK?
Is this process correct to assign=C2= =A0IP=C2=A0 and then device to DPDK?


on VM1:
=C2=A0After star= ting the DPDK application, I can see a tap0 device created in kernel mode v= ia 'ip add show'.Then I attached this interface with network namesp= ace=C2=A0via:

ip netns add ns0
ip link set tap0 netns ns0
ip n= etns exec ns0 ip addr add <IPV4 Address> dev tap0
ip netns exec n= s0 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 c= onfiguration 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=C2=A0work.=
Any help/pointer is really appreciated.


--00000000000041ccd405f93b1c1f--