Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
4621 Discussions

XL710 Stops Receiving Packets After a Particular PPPoE Packet

SM8
Beginner
‎07-19-2017 11:11 PM
1,607 Views

HI Everyone,

We are using XL710 hardware on Linux 4.1.20 kernel.

We have an issue where the following behavior is noticed.

  • When we send a simple loop back traffic to the XL710, it works fine.
  • When a specific PPPoE packet is sent from an external port to the XL710, on Linux we notice that the XL710 driver has no response. There is no interrupt is raised for this received packet.
  • After the above condition, XL710 stops receiving any packet.

Here is the packet contents for a good packet and the failing packet.

I can send any number of good packets, and XL710 is able to received it.

After I send a single failing packet, XL710 stop receiving packets. In fact, it does not receive even the good packets after this.

Good Packet:

Frame 2: 128 bytes on wire (1024 bits), 124 bytes captured (992 bits) on interface 0

Interface id: 0 (\\.\pipe\view_capture_172-27-5-51_6_89_07182017_154149)

Encapsulation type: Ethernet (1)

Arrival Time: Jul 18, 2017 15:41:13.680293000 India Standard Time

[Time shift for this packet: 0.000000000 seconds]

Epoch Time: 1500372673.680293000 seconds

[Time delta from previous captured frame: 0.496532000 seconds]

[Time delta from previous displayed frame: 0.496532000 seconds]

[Time since reference or first frame: 0.496532000 seconds]

Frame Number: 2

Frame Length: 128 bytes (1024 bits)

Capture Length: 124 bytes (992 bits)

[Frame is marked: False]

[Frame is ignored: False]

[Protocols in frame: eth:ethertype:mpls:pwethheuristic:pwethcw:eth:ethertype:vlan:ethertype:vlan:ethertype:pppoes:ppp:ipcp]

Ethernet II, Src: Performa_00:00:02 (00:10:94:00:00:02), Dst: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

Destination: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

Address: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

Source: Performa_00:00:02 (00:10:94:00:00:02)

Address: Performa_00:00:02 (00:10:94:00:00:02)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

Type: MPLS label switched packet (0x8847)

MultiProtocol Label Switching Header, Label: 1 (Router Alert), Exp: 0, S: 1, TTL: 64

0000 0000 0000 0000 0001 .... .... .... = MPLS Label: Router Alert (1)

.... .... .... .... .... 000. .... .... = MPLS Experimental Bits: 0

.... .... .... .... .... ...1 .... .... = MPLS Bottom Of Label Stack: 1

.... .... .... .... .... .... 0100 0000 = MPLS TTL: 64

PW Ethernet Control Word

Sequence Number: 0

Ethernet II, Src: Performa_00:00:03 (00:10:94:00:00:03), Dst: Superlan_00:00:01 (00:00:01:00:00:01)

Destination: Superlan_00:00:01 (00:00:01:00:00:01)

Address: Superlan_00:00:01 (00:00:01:00:00:01)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

Source: Performa_00:00:03 (00:10:94:00:00:03)

Address: Performa_00:00:03 (00:10:94:00:00:03)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

Type: 802.1Q Virtual LAN (0x8100)

802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 100

000. .... .... .... = Priority: Best Effort (default) (0)

...0 .... .... .... = CFI: Canonical (0)

.... 0000 0110 0100 = ID: 100

Type: 802.1Q Virtual LAN (0x8100)

802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 100

000. .... .... .... = Priority: Best Effort (default) (0)

...0 .... .... .... = CFI: Canonical (0)

.... 0000 0110 0100 = ID: 100

Type: PPPoE Session (0x8864)

PPP-over-Ethernet Session

0001 .... = Version: 1

.... 0001 = Type: 1

Code: Session Data (0x00)

Session ID: 0x0001

Payload Length: 74

Point-to-Point Protocol

Protocol: Internet Protocol Control Protocol (0x8021)

PPP IP Control Protocol

Code: Configuration Request (1)

Identifier: 2 (0x02)

Length: 10

Options: (6 bytes), IP address

IP address: 0.0.0.0

Type: IP address (3)

Length: 6

IP Address: 0.0.0.0

Failing Packet:

Frame 1: 128 bytes on wire (1024 bits), 124 bytes captured (992 bits) on interface 0

Interface id: 0 (\\.\pipe\view_capture_172-27-5-51_6_89_07182017_154149)

Encapsulation type: Ethernet (1)

Arrival Time: Jul 18, 2017 15:41:13.183761000 India Standard Time

[Time shift for this packet: 0.000000000 seconds]

Epoch Time: 1500372673.183761000 seconds

[Time delta from previous captured frame: 0.000000000 seconds]

[Time delta from previous displayed frame: 0.000000000 seconds]

[Time since reference or first frame: 0.000000000 seconds]

Frame Number: 1

Frame Length: 128 bytes (1024 bits)

Capture Length: 124 bytes (992 bits)

[Frame is marked: False]

[Frame is ignored: False]

[Protocols in frame: eth:ethertype:mpls:pwethheuristic:pwethcw:eth:ethertype:vlan:ethertype:vlan:ethertype:pppoes:ppp:ipcp]

Ethernet II, Src: Performa_00:00:02 (00:10:94:00:00:02), Dst: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

Destination: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

Address: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

Source: Performa_00:00:02 (00:10:94:00:00:02)

Address: Performa_00:00:02 (00:10:94:00:00:02)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individual address (unicast)

Type: MPLS label switched packet (0x8847)

MultiProtocol Label Switching Header, Label: 1 (Router Alert), Exp: 0, S: 1, TTL: 64

0000 0000 0000 0000 0001 .... .... .... = MPLS Label: Router Alert (1)

.... .... .... .... .... 000. .... .... = MPLS Experimental Bits: 0

.... .... .... .... .... ...1 .... .... = MPLS Bottom Of Label Stack: 1

.... .... .... .... .... .... 0100 0000 = MPLS TTL: 64

PW Ethernet Control Word

Sequence Number: 0

Ethernet II, Src: Performa_00:00:03 (00:10:94:00:00:03), Dst: Superlan_00:00:01 (00:00:01:00:00:01)

Destination: Superlan_00:00:01 (00:00:01:00:00:01)

Address: Superlan_00:00:01 (00:00:01:00:00:01)

.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

.... ...0 .... .... .... .... = IG bit: Individ...

0 Kudos

Link Copied

9 Replies
idata
Employee
‎07-20-2017 07:10 PM
567 Views

Hi Sadashivan,

 

 

Thank you for posting at Wired Communities. What is the exact XL710 network adapter? Is it an onboard or standalone network adapter? What is the exact driver and firmware version?

 

 

Thanks,

 

sharon

 

0 Kudos
Copy link
SM8
Beginner
‎07-23-2017 12:59 AM
567 Views
In response to idata

Hi Sharon,

Thank you for your response.

We have the XL710 as an onboard IC in our product.

a) Driver. We are using the XL710 driver from Linux 4.1.20 release.

b) Firmware. Here is the firmware details (obtained using the './intel-netdev-eeupdate /NIC=4 /ADAPTERINFO' command)

Firmware Version: FW:5.0 API:1.5

NVM Version: 5.02 MAP3.75

Regards,

Sadashivan

In response to idata
0 Kudos
Copy link
idata
Employee
‎07-23-2017 07:32 PM
567 Views
In response to SM8

Hi Sadashivan,

Thank you for the information. I will check on this. Can you also share what is the brand and model of your product? Thanks.

regards,

sharon

 

In response to SM8
0 Kudos
Copy link
idata
Employee
‎07-26-2017 07:07 PM
567 Views
In response to SM8

Hi Sadashivan,

 

 

Just to double check, can you try upgrade the firmware version of the XL710 to latest version post on our web? Please feel free to update me.

 

https://downloadcenter.intel.com/download/24769/Non-Volatile-Memory-NVM-Update-Utility-for-Intel-Ethernet-Converged-Network-Adapter-XL710-and-X710-Series?product=83950

 

 

Thank you.

 

 

regards,

 

sharon

 

In response to SM8
0 Kudos
Copy link
idata
Employee
‎07-27-2017 10:54 PM
567 Views
In response to SM8

Hi Sadashivan,

 

 

Please feel free to update me if you have tried the upgrade and what is the current status of the NIC. Thank you.

 

 

regards,

 

sharon
In response to SM8
0 Kudos
Copy link
SM8
Beginner
‎08-02-2017 01:02 AM
567 Views
In response to SM8

HI Sharon,

Sorry for the delay in getting back on this topic.

Yes, after the firmware update, things are working fine now.

Can you share some inputs on what are the fixes that may have made it work now?

Regards,

Sadashivan

In response to SM8
0 Kudos
Copy link
idata
Employee
‎08-02-2017 08:10 PM
567 Views
In response to SM8

Hi Sadashivan,

 

 

Thank you for the update and I am glad that the firmware update resolved the issue. I will further check for you about the fixes.

 

 

regards,

 

sharon

 

In response to SM8
0 Kudos
Copy link
idata
Employee
‎08-15-2017 05:28 PM
567 Views
In response to SM8

Hi Sadashivan,

 

Please let me know if you need further clarification.

 

 

regards,

 

sharon

 

In response to SM8
0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.