Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 10 of 10
  1. #1

    Question 802.1AX/802.3AD - abnormal LACP packet size?

    Region : France

    Model : TL-SG2424

    Hardware Version : V1

    Firmware Version : 1.0.0 Build 20140126 Rel.34563

    ISP :


    Hi there,
    This is my first post on this forum so please pardon any unexpected behavior from my side.

    I'm a the owner of several TL-SG2008 1.0 (firmware: 1.0.0 Build 20140126 Rel.34563) smart switches (not able to select this model number from the drop down list).
    I have them from a few months now and wanted since configure the feature I mainly bought them for: LACP.

    As I have had difficulties since weeks to understand why my setup isn't working (reviewed from all possible angles), I started to look for similar issues on the Internet and found the following topic FreeBSD 10-stable (r274577) LACP / IEEE 802.3ad with TP-Link TL-SG2008 - not working.

    I then did a couple of packet captures on different brands equipment to analyze LACP traffic. On one side I did setup LACP on one of the equipment port, on the other side I connected a host with a NIC in promiscious mode and sniffed all traffic.

    And indeed the TL-SG2008 is sending 128 bytes packets when other equipment are sending 124 bytes packets- the extra 4 bytes are at the end of the packet:
    Code:
    TP-Link
    0000   01 80 c2 00 00 02 e8 de 27 6b 9d 1b 88 09 01 01  ........'k......
    0010   01 14 80 00 e8 de 27 6b 9d 1b 07 7e 80 00 00 07  ......'k...~....
    0020   c5 00 00 00 02 14 00 00 00 00 00 00 00 00 00 00  ................
    0030   00 00 00 00 06 00 00 00 03 10 00 00 00 00 00 00  ................
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00 80 31 60 7c  .............1`|
    
    FreeBSD
    0000   01 80 c2 00 00 02 00 00 24 cf ec 9a 88 09 01 01  ........$.......
    0010   01 14 80 00 00 00 24 cf ec 9a 01 2b 80 00 00 03  ......$....+....
    0020   4d 00 00 00 02 14 ff ff 00 00 00 00 00 00 00 00  M...............
    0030   ff ff 00 00 00 00 00 00 03 10 00 00 00 00 00 00  ................
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00              ............
    
    HP
    0000   01 80 c2 00 00 02 a0 b3 cc 32 12 b7 88 09 01 01  .........2......
    0010   01 14 12 a0 a0 b3 cc 32 12 a0 ff ff 00 00 00 09  .......2........
    0020   75 00 00 00 02 14 00 00 00 00 00 00 00 00 00 00  u...............
    0030   00 00 00 09 86 00 00 00 03 10 27 10 00 00 00 00  ..........'.....
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00              ............
    
    Extreme Networks
    0000   01 80 c2 00 00 02 00 04 96 1f 50 6a 88 09 01 01  ..........Pj....
    0010   01 14 91 f4 00 04 96 1f 50 6a 80 00 00 00 00 12  ........Pj......
    0020   47 00 00 00 02 14 00 00 00 00 00 00 00 00 00 00  G...............
    0030   00 00 00 00 3b 00 00 00 03 10 00 02 00 00 00 00  ....;...........
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00              ............
    What this implies it that LACP is not working in my setup, which is a critical issue as this is a feature I mainly bought these switches for.
    Did anyone expect such behavior as well? Or maybe can tell if this 128 bytes behavior is also happening with other TP-Link switches?

    I'm not sure yet but these extra 4 bytes look like a CRC32 added at the end of the packet. This would correspond to the Frame Check Sequence (FCS) specified in the 802.3AD/802.1AX standard, but then shouldn't this FCS be added/stripped by the underlying MAC layer directly? And if so, aren't we having an extra FCS here, added somehow alongside the effective FCS which is added/stripped by the underlying MAC layer, making thus this packet 128 bytes long instead of 124 as on other equipment?

    Thanks in advance for your help.
    Best regards,

  2. #2

    Same problem.

    I have the exatly the same problem.
    Have you tried to contact TP-LINK support?

    Quote Originally Posted by piotr3k View Post
    Region : France

    Model : TL-SG2424

    Hardware Version : V1

    Firmware Version : 1.0.0 Build 20140126 Rel.34563

    ISP :


    Hi there,
    This is my first post on this forum so please pardon any unexpected behavior from my side.

    I'm a the owner of several TL-SG2008 1.0 (firmware: 1.0.0 Build 20140126 Rel.34563) smart switches (not able to select this model number from the drop down list).
    I have them from a few months now and wanted since configure the feature I mainly bought them for: LACP.

    As I have had difficulties since weeks to understand why my setup isn't working (reviewed from all possible angles), I started to look for similar issues on the Internet and found the following topic FreeBSD 10-stable (r274577) LACP / IEEE 802.3ad with TP-Link TL-SG2008 - not working.

    I then did a couple of packet captures on different brands equipment to analyze LACP traffic. On one side I did setup LACP on one of the equipment port, on the other side I connected a host with a NIC in promiscious mode and sniffed all traffic.

    And indeed the TL-SG2008 is sending 128 bytes packets when other equipment are sending 124 bytes packets- the extra 4 bytes are at the end of the packet:
    Code:
    TP-Link
    0000   01 80 c2 00 00 02 e8 de 27 6b 9d 1b 88 09 01 01  ........'k......
    0010   01 14 80 00 e8 de 27 6b 9d 1b 07 7e 80 00 00 07  ......'k...~....
    0020   c5 00 00 00 02 14 00 00 00 00 00 00 00 00 00 00  ................
    0030   00 00 00 00 06 00 00 00 03 10 00 00 00 00 00 00  ................
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00 80 31 60 7c  .............1`|
    
    FreeBSD
    0000   01 80 c2 00 00 02 00 00 24 cf ec 9a 88 09 01 01  ........$.......
    0010   01 14 80 00 00 00 24 cf ec 9a 01 2b 80 00 00 03  ......$....+....
    0020   4d 00 00 00 02 14 ff ff 00 00 00 00 00 00 00 00  M...............
    0030   ff ff 00 00 00 00 00 00 03 10 00 00 00 00 00 00  ................
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00              ............
    
    HP
    0000   01 80 c2 00 00 02 a0 b3 cc 32 12 b7 88 09 01 01  .........2......
    0010   01 14 12 a0 a0 b3 cc 32 12 a0 ff ff 00 00 00 09  .......2........
    0020   75 00 00 00 02 14 00 00 00 00 00 00 00 00 00 00  u...............
    0030   00 00 00 09 86 00 00 00 03 10 27 10 00 00 00 00  ..........'.....
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00              ............
    
    Extreme Networks
    0000   01 80 c2 00 00 02 00 04 96 1f 50 6a 88 09 01 01  ..........Pj....
    0010   01 14 91 f4 00 04 96 1f 50 6a 80 00 00 00 00 12  ........Pj......
    0020   47 00 00 00 02 14 00 00 00 00 00 00 00 00 00 00  G...............
    0030   00 00 00 00 3b 00 00 00 03 10 00 02 00 00 00 00  ....;...........
    0040   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0050   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0060   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    0070   00 00 00 00 00 00 00 00 00 00 00 00              ............
    What this implies it that LACP is not working in my setup, which is a critical issue as this is a feature I mainly bought these switches for.
    Did anyone expect such behavior as well? Or maybe can tell if this 128 bytes behavior is also happening with other TP-Link switches?

    I'm not sure yet but these extra 4 bytes look like a CRC32 added at the end of the packet. This would correspond to the Frame Check Sequence (FCS) specified in the 802.3AD/802.1AX standard, but then shouldn't this FCS be added/stripped by the underlying MAC layer directly? And if so, aren't we having an extra FCS here, added somehow alongside the effective FCS which is added/stripped by the underlying MAC layer, making thus this packet 128 bytes long instead of 124 as on other equipment?

    Thanks in advance for your help.
    Best regards,

  3. #3

    Support contacted yesterday (2015-02-12)

    Quote Originally Posted by Nicholas View Post
    I have the exatly the same problem.
    Have you tried to contact TP-LINK support?
    Hi Nicholas,

    Yes indeed, I went through the tech support contact form yesterday but no email or anything received so far.

    Are you expecting this issue with a TL-SG2008 or another model?

  4. #4

    Red face New firmware in test

    Quote Originally Posted by piotr3k View Post
    Hi Nicholas,

    Yes indeed, I went through the tech support contact form yesterday but no email or anything received so far.

    Are you expecting this issue with a TL-SG2008 or another model?
    Just to let anyone reading this topic know that I've received yesterday a new firmware from TP-LINK Support team which should fix this problem.

    After installation, I am now able to have a working LACP setup, which is great news!
    Some errors are reported on the remote network LACP interfaces, but I'll have to dig this deeper later as for now performances are good after some large files transfer tests.

    So far, so good :-)
    Thank you support team for the responsiveness, much appreciated!

  5. #5
    Quote Originally Posted by piotr3k View Post
    Just to let anyone reading this topic know that I've received yesterday a new firmware from TP-LINK Support team which should fix this problem.

    After installation, I am now able to have a working LACP setup, which is great news!
    Some errors are reported on the remote network LACP interfaces, but I'll have to dig this deeper later as for now performances are good after some large files transfer tests.

    So far, so good :-)
    Thank you support team for the responsiveness, much appreciated!
    Hi piotr3k would you be so kind and send me the test firmware?
    I came across the same problem it seems.

  6. #6
    Quote Originally Posted by Celoxocis View Post
    Hi piotr3k would you be so kind and send me the test firmware?
    I came across the same problem it seems.
    Why you do not download the latest firmware from tp-link website?

  7. #7
    Quote Originally Posted by TPTHZ View Post
    Why you do not download the latest firmware from tp-link website?
    I am runn the latest version. However the LACP isn't working.
    See my thread here: http://forum.tp-link.com/showthread....se-from-Switch

  8. #8
    Quote Originally Posted by Celoxocis View Post
    Hi piotr3k would you be so kind and send me the test firmware?
    I came across the same problem it seems.
    Hi @Celoxocis,

    Since my initial message TP-LINK published a second version of the stock firmware, and even a third one:
    http://www.tp-link.com/lb/download/T....html#Firmware

    The second one is the official version to fix the LACP issue. The third one add some nice security features.
    If upgrading to the latest version doesn't help, IMHO contacting the support will be necessary.

  9. #9
    Quote Originally Posted by piotr3k View Post
    Hi @Celoxocis,

    Since my initial message TP-LINK published a second version of the stock firmware, and even a third one:
    http://www.tp-link.com/lb/download/T....html#Firmware

    The second one is the official version to fix the LACP issue. The third one add some nice security features.
    If upgrading to the latest version doesn't help, IMHO contacting the support will be necessary.
    thanks for getting back to me. I wasn't sure if your discovery made it into the newer firmwares or you were running a developer firmware.
    i've tried everything. to get it to work. except downgrading to an older firmware.
    you can have a look at my setup here

    a
    lso how does someone contact the proper support?
    there is one for every country. to confusing.
    it's definitely not my OS (Ubuntu Server 16.04 LTS) that one is used in enterprise environments.
    nor my NIC's. they are both Intel e1000

    Code:
    02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

  10. #10
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Quote Originally Posted by Celoxocis View Post
    also how does someone contact the proper support?
    there is one for every country. to confusing.
    Yes, every country has its first-level support, for example by live chat, phone/hotline and email, so you don't have to learn Chinese to talk to them.
    Sometimes they read here, too, but the direct way would be to contact them online or by phone. See your country's website, click on "Support".


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.