All of
 help / color / mirror / Atom feed
From: Fujinaka, Todd <>
Subject: [Intel-wired-lan] [E1000-devel] Traffic not passing for VLAN ID >= 32 on the I350 SR-IOV enabled NIC
Date: Tue, 27 Jul 2021 15:04:28 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Can you please file this through your company contact? I think you have very specific requirements that we can't discuss on a public mailing list.

Todd Fujinaka
Software Application Engineer
Data Center Group
Intel Corporation
todd.fujinaka at

-----Original Message-----
From: Yuvaraj Ranganathan via E1000-devel <> 
Sent: Monday, July 26, 2021 11:23 PM
To:; intel-wired-lan at
Cc: Pushp Saurav <>
Subject: [E1000-devel] Traffic not passing for VLAN ID >= 32 on the I350 SR-IOV enabled NIC

Hi Team,

With the SR-IOV enabled on I350 NIC which has 4 VF's, on configuring VLAN ID from range 1 to 31 on the VM interface, network traffic is fine and no issues. When trying to create an interface with VLAN ID >= 32 on the VM, traffic is not passing to that interface and as per HW specs, VLAN ID's from 1 to 4096 are supported.

VM's interface is directly mapped to one of the VF on I350 NIC. I am using IGB PF driver version 5.7.2(latest).

Could somebody please help!

Thanks in advance,

Juniper Business Use Only

E1000-devel mailing list
E1000-devel at
To learn more about Intel Ethernet, visit

  reply	other threads:[~2021-07-27 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  6:23 [Intel-wired-lan] " Yuvaraj Ranganathan
2021-07-27 15:04 ` Fujinaka, Todd [this message]
2021-07-27 16:04   ` [Intel-wired-lan] [E1000-devel] " Fujinaka, Todd
2021-07-29  2:11 ` Laurent Dumont
2021-07-29  9:37   ` Yuvaraj Ranganathan
2021-07-29 12:34     ` Laurent Dumont

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: [Intel-wired-lan] [E1000-devel] Traffic not passing for VLAN ID >= 32 on the I350 SR-IOV enabled NIC' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.