>-----Original Message-----
>From: Vijay Agrawal [mailto:vagra...@ixiacom.com]
>Sent: Sunday, February 16, 2014 10:17 PM
>To: Fujinaka, Todd; e1000-de...@lists.sf.net
>Subject: Re: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket ,
>
>Hi Todd,
>
>We are really blocked for this , can you please suggest a
>fix for this  for any possible  workaround.

If you are using kernel < 2.6.36 edit kcompat.h and make sure you have:
#define HAVE_8021P_SUPPORT

Inside the section for kernels < 2.6.36. Rebuild the driver and give it a try - 
this should allow you to see the vlan packets.

Thanks,
Emil

>Any suggestion on this would be really helpful.
>
>Thanks & Regards
>  Vijay Agrawal
>
>-----Original Message-----
>From: Vijay Agrawal
>Sent: 04 February 2014 18:25
>To: Fujinaka, Todd; e1000-de...@lists.sf.net
>Subject: RE: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket
>
>Hi Todd,
>
>Basically it's only with vlan that 10G interface is not
>working and we are using the latest driver ixgbe-3.18.7.
>In last mail the packet was actually sent without VLAN so
>there was no issue.
>I have tested it more , and the  problem reduced to this :
>       With VLAN the 10G driver is not accepting the vlan
>tagged packets unless that vlan is configured on the
>physical interface, we are using PF_PACKET sockets here and
>we don't want to       configure VLAN physically on the
>interface. No such limitation exists on 1 G driver (igbvf).
>
>Here I have modified the simple program to explain the
>problem in  some more detail.
>It has two programs here , sender and receiver.
>
>Suppose we are sending  packets on interface eth0 and
>receiving on interface eth1.
>Run ethereal on interface eth0 and eth1 .
>
>Run  Receiver on one interface as
># ./receiver interface_name
>Example  :
>#  ./receiver  eth1
>
>Run sender on one interface as
># ./sender interface_name  with_vlan (1/0)  ( 1(one)  will
>add vlan , 0(zero) will not).
>Example  :
>#  ./sender  eth0 1
>
>Now you will be able to observer that on interface eth0 ,
>the ethereal will show that one arp request is sent with
>vlan in it , but at the same time you will receive nothing
>on eth1, neither on ethereal nor , receiver program will say
>anything.
>
>Now just run sender again without vlan as #./sender eth0  0
>
>Now u will observe that packet is successfully sent and
>received , we can capture the packet on eth1 on ethereal and
>receiver program will also dump the packet on console.
>
>Thanks & Regards
>  Vijay Agrawal
>
>-----Original Message-----
>From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
>Sent: 30 January 2014 03:25
>To: Vijay Agrawal; e1000-de...@lists.sf.net
>Subject: RE: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket
>
>We don't seem to have any issues:
>
>>From the sender:
># ./test eth2
>
> buffer is : FFFFFFFF  FFFFFFFF  FFFFFFFF  FFFFFFFF
>FFFFFFFF  FFFFFFFF  11  11  11  11  11  11  08  06  00  01
>08  00  06  04  00  01  11  11  11  11  11  11  11  11  11
>11  00  00  00  00  00  00  22  22  22  22  PF_PACKET: ARP
>request sent 42 bytes
>
>On receiver:
># tcpdump -i eth2 -xxv
>tcpdump: listening on eth2, link-type EN10MB (Ethernet),
>capture size 65535 bytes
>06:24:56.538905 ARP, Ethernet (len 6), IPv4 (len 4), Request
>who-has 34.34.34.34 tell 17.17.17.17, length 46
>       0x0000:  ffff ffff ffff 1111 1111 1111 0806 0001
>       0x0010:  0800 0604 0001 1111 1111 1111 1111 1111
>       0x0020:  0000 0000 0000 2222 2222 0000 0000 0000
>       0x0030:  0000 0000 0000 0000 0000 0000
>
>Todd Fujinaka
>Software Application Engineer
>Networking Division (ND)
>Intel Corporation
>todd.fujin...@intel.com
>(503) 712-4565
>
>
>-----Original Message-----
>From: Vijay Agrawal [mailto:vagra...@ixiacom.com]
>Sent: Tuesday, January 28, 2014 10:07 PM
>To: Fujinaka, Todd; e1000-de...@lists.sf.net
>Subject: RE: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket
>
>Hi  Todd,
>
>Just wanted to help  you to understand the issue we are
>facing .
>With static VLAN configured on the interface , hardware
>sends the packet but vlan is stripped.
>With PF_PACKET socket where we are constructing entire
>Ethernet packet our self , the packet is dropped by the
>hardware.
>
>I have attached a simple C program which uses PF_PACKET
>SOCKET to send one test ARP packet with VLAN, and you can
>clearly observe that packet is dropped.
>
>You can compile it with
>Sudo make compile
>Run it with
>
>./test  "interface name (example eth0)"
>
>I hope it will help you to quickly identify the issue , and
>may be you can suggest something to fix it or if you can
>confirm if this is as expected  as per design.
>
>Thanks & Regards
>  Vijay Agrawal
>
>-----Original Message-----
>From: Vijay Agrawal
>Sent: 29 January 2014 10:30
>To: 'Fujinaka, Todd'; e1000-de...@lists.sf.net
>Subject: RE: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket
>
>Hi Todd,
>
>Thanks a lot for the response.
>Can you please explain this a bit more.
>When you say you are stripping the VLAN tags , so  the
>packet with VLAN tag should go out without VLAN  tag , but
>here we observe that no packet is going out , so it look
>like the hardware drops the VLAN tag packet, we see no
>packet on the ethereal. Can you please explain this ?
>Is there any work around solution to work with VLAN? Or with
>this driver it's just not possible.
>
>Thanks again for your quick response .
>
>Thanks & Regards
>  Vijay Agrawal
>
>-----Original Message-----
>From: Fujinaka, Todd [mailto:todd.fujin...@intel.com]
>Sent: 29 January 2014 02:04
>To: Vijay Agrawal; e1000-de...@lists.sf.net
>Subject: RE: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket
>
>Our hardware strips VLAN tags in order to support Data
>Center Bridging (I think the details are in 802.1Q for DCB).
>DCB uses the same offset as VLAN tags and if we didn't strip
>the tags we couldn't have interoperability between endpoints
>that had DCB enabled and not enabled.
>
>Todd Fujinaka
>Software Application Engineer
>Networking Division (ND)
>Intel Corporation
>todd.fujin...@intel.com
>(503) 712-4565
>
>
>-----Original Message-----
>From: Vijay Agrawal [mailto:vagra...@ixiacom.com]
>Sent: Monday, January 27, 2014 10:02 PM
>To: e1000-de...@lists.sf.net
>Subject: [E1000-devel] ixgbe-3.17.3 :VLAN tagged packets
>does not work when using PF-PACKET socket
>
>Hi ,
>
>We are observing a issue with this driver , we are using PF-
>Packet sockets for sending receiving Ethernet packets, but
>if the packet is  Vlan tagged it is not sent/received on the
>interface. Neither the packet is seen on the ethereal
>capture. Here we are just using PF-PACKET socket and no IP
>and Vlan is configured on the physical interface.
>The same test  if we run on 1 G node it works , so as it
>seems there is some limitations with this 10G driver.
>Can you please help.
>
>Thanks & Regards
>  Vijay Agrawal
>
>
>------------------------------------------------------------
>------------------
>Managing the Performance of Cloud-Based Applications
>Take advantage of what the Cloud has to offer - Avoid Common
>Pitfalls.
>Read the Whitepaper.
>http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/
>4140/ostg.clktrk
>_______________________________________________
>E1000-devel mailing list
>E1000-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/e1000-devel
>To learn more about Intel&#174; Ethernet, visit
>http://communities.intel.com/community/wired

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to