From: Jagan P <jagan2.p@altran.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK support for vlan id 0
Date: Wed, 12 May 2021 15:40:25 +0000 [thread overview]
Message-ID: <MAXPR01MB3278D79A86E52C9D103A1CC1DC529@MAXPR01MB3278.INDPRD01.PROD.OUTLOOK.COM> (raw)
Hi,
We were trying to forward packets with vlan id as 0. But the packet is getting altered when we do so.
The IP flag and the destination port fields are getting changed. We doubt if this is happening in DPDK because till the rte_eth_tx_burst API, the packet is proper.
But the packet captured at the destination is altered.
Could you please let us know if there is support in DPDK for forwarding packet with vlan id 0 or if we are missing something.
Packet at rte_eth_tx_burst:
dump mbuf at 0x1706dad00, iova=0x1706dad80, buf_len=2304
pkt_len=252, ol_flags=0xf0000000000181, nb_segs=1, port=0, vlan_tci=0, ptype=0x211
segment at 0x1706dad00, data=0x1706dae04, len=252, off=132, refcnt=1
Dump data at [0x1706dae04], len=200
00000000: 00 10 94 00 00 05 00 01 02 03 04 05 81 00 00 00 | ................
00000010: 08 00 45 00 00 EA 00 02 00 00 3F 11 00 00 02 02 | ..E.......?.....
00000020: 02 02 05 05 05 02 62 A4 62 A3 00 D6 0E F2 00 00 | ......b.b.......
00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
000000A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
000000B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
000000C0: 00 00 00 00 00 00 00 00
Packet captured at spirent(destination):
00 10 94 00 00 05 00 01 02 03 04 05 81 00 00 00
08 00 45 00 00 EA 00 02 6e fe 3F 11 00 00 02 02
02 02 05 05 05 02 62 A4 f5 f8 00 D6 0E F2 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Thanks,
Jagan P
=====================================================
Please refer to https://northamerica.altran.com/email-disclaimer
for important disclosures regarding this electronic communication.
=====================================================
next reply other threads:[~2021-05-17 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 15:40 Jagan P [this message]
2021-05-17 8:45 ` Muhammad Zain-ul-Abideen
2021-05-17 11:45 ` Jagan P
2021-05-17 12:02 ` Muhammad Zain-ul-Abideen
2021-05-17 15:24 ` Jagan P
2021-05-17 15:28 ` Muhammad Zain-ul-Abideen
2021-05-17 18:32 ` Jagan P
2021-05-17 18:52 ` Muhammad Zain-ul-Abideen
2021-05-18 6:47 ` Jagan P
2021-05-18 8:46 ` Muhammad Zain-ul-Abideen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MAXPR01MB3278D79A86E52C9D103A1CC1DC529@MAXPR01MB3278.INDPRD01.PROD.OUTLOOK.COM \
--to=jagan2.p@altran.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).