From: Stephen Hemminger <stephen@networkplumber.org>
To: waqas ahmed <waqasahmed1471@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Frame Check Sequence is incorrect?
Date: Fri, 31 Aug 2018 13:07:56 -0700 [thread overview]
Message-ID: <20180831130756.135f1a3b@xeon-e3> (raw)
In-Reply-To: <CAMr3K=eRnfQg=1m_DqmQ9ccw0mrADJ+xeLWE8t7JJ6qa1V4oZw@mail.gmail.com>
On Fri, 31 Aug 2018 23:19:38 +0500
waqas ahmed <waqasahmed1471@gmail.com> wrote:
> Hi Everyone,
> i have kvm with two ports, i am getting rtp stream from port 0 and just
> change source ip of each packet and recalculate ipv4 checksum. then same
> pkt mbuf is got rte_eth_tx_burst from port1.
> but on vm2 wireshark shows that Frame check sequence is incorrect, that
> seems that while getting same mbuf out from port1 cant get FCS
> recalculated? by emulated nic.
> kind regards and any help is appreciated.
almost all nic's inside a hypervisor do not support getting FCS.
FCS is used when transferring data over physical wires, and really makes
no sense in a virtual environment.
prev parent reply other threads:[~2018-08-31 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 18:19 waqas ahmed
2018-08-31 20:07 ` Stephen Hemminger [this message]
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=20180831130756.135f1a3b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=waqasahmed1471@gmail.com \
/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).