* [dpdk-users] Frame Check Sequence is incorrect?
@ 2018-08-31 18:19 waqas ahmed
2018-08-31 20:07 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: waqas ahmed @ 2018-08-31 18:19 UTC (permalink / raw)
To: users
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-users] Frame Check Sequence is incorrect?
2018-08-31 18:19 [dpdk-users] Frame Check Sequence is incorrect? waqas ahmed
@ 2018-08-31 20:07 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2018-08-31 20:07 UTC (permalink / raw)
To: waqas ahmed; +Cc: users
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-08-31 20:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-31 18:19 [dpdk-users] Frame Check Sequence is incorrect? waqas ahmed
2018-08-31 20:07 ` Stephen Hemminger
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).