DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shaham Fridenberg <ShahamF@Radware.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] SR-IOV: ixgbe spoofed packets
Date: Tue, 28 Apr 2015 11:51:12 +0000	[thread overview]
Message-ID: <2E654B490240B7449C846A96A8D8FE0C414FC98D@ILMB1.corp.radware.com> (raw)

Hey All,

I hope that this is the right address for my question.

I currently have a VM on Cisco server that runs KVM and SR-IOV is enabled.

4 VFs are attached to this VM and I try to send ARPs from SPIRENT traffic generator to the VM which its ports are VLAN tagged.

Although I turned off spoof checking on the VFs (I used 'ip link set eth17 vf 0 spoofchk off' command), I still get spoofed packets detected on the ixgbe driver in dmesg:

ixgbe 0000::0c:00.0 eth17: 2 Spoofed packets detected

I read online that spoof detection is enabled by default (on compilation) on ixgbe driver when SR-IOV is active.

Any idea how to overcome this issue?

If any more information needed please let me know.

Thanks,
Shaham

                 reply	other threads:[~2015-04-28 11:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2E654B490240B7449C846A96A8D8FE0C414FC98D@ILMB1.corp.radware.com \
    --to=shahamf@radware.com \
    --cc=dev@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).