Some more discovery.
That flag PKT_TX_VLAN_PKT eventually send the following command to the
chips (ixgbe_xmit_pkts(), tx_desc_vlan_flags_to_cmdtype()) . Is this
actually adding a VLAN tag during tx ?
#define IXGBE_ADVTXD_DCMD_VLE IXGBE_TXD_CMD_VLE /* VLAN pkt
enable */
#define IXGBE
Stephen,
I added that to the l2fwd main.c and it is still not received by the
Spirent. I obtained the stat using rte_eth_stats_get() and printout the
following when I send only one VLAN pkt
ipackets: increased by 1
opackets: no change (pkt not sent out by the device)
ierrors, oerrors, otxerror, ot
On Thu, 23 Jan 2014 11:27:14 -0800
James Yu wrote:
> Hi Daniel,
>
> Untagged traffic could be looped back. I am doing a one-directional loop
> back. In the Frame tabe of the StreamBlock editor, I did the following
> stream1:
> destination address: MAC address of the receiving port of the gu
Hi Daniel,
Untagged traffic could be looped back. I am doing a one-directional loop
back. In the Frame tabe of the StreamBlock editor, I did the following
stream1:
destination address: MAC address of the receiving port of the guest
VM. (obtained from the debug print out when l2fwd is started,
Hi James,
Did you try a non-tagged traffic? I suspect this is the limitation of the
l2fwd or the requirements of Spirent. From my experience with Ixia, the L2
forward device must implement the ARP protocol (at least a subset of it).
Also, notice that the l2fwd example sets the destination MAC add
I could not pass tagged traffic through the l2fwd program running inside a
CentOS VM. The l2fwd program reported sending out all the packets received
from one port to the other port. But the outside Spirent tester could not
receive a packet at all. I am wondering maybe the tagged packets are
droppe
6 matches
Mail list logo
