New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant capture packets using dpdk-pdump #10
Comments
Hi @vaniaprkl , I know that a few people have used dpdk-testpmd okay, but I'm not aware of anyone using dpdk-pdump. The port of the AMD-Xilinx DPDK QDMA drivers to OpenNIC was contributed by someone in the community. Getting that to work might require some additional changes. --Chris |
Hi @vaniaprkl , I chatted with someone who did use a combination of dpdk-testpmd + dpdk-pdump recently to test. They used testpmd in --interactive mode. They said dpdk-testpmd showed two ports forwarding packets back and forth. They tried Best regards, |
One other note is that testpmd might be expecting packets with a matching destination MAC+IP, but we don't know that for certain. |
Hi Team,
Please let me know what changes to be done so that the RX packets are also gets incremented.? |
Hi,
We are running into an issue trying to capture packets with dpdk-pdump.
testpmd was run as the primary process using the following command below:
Packets were being transmitted to this port at all times. The corresponding pdump was started against the same device and its output shows it is indeed chained to testpmd. Closing testpmd stops pdump window as well.
What is the problem here? Any suggestions?
The text was updated successfully, but these errors were encountered: