Skip to content

Bug #911 continue on get l2len protcol is zero#941

Merged
fklassen merged 3 commits into4.5.2-beta1from
Bug_#911_continue_on_get_l2len_protcol_is_zero
Jul 4, 2025
Merged

Bug #911 continue on get l2len protcol is zero#941
fklassen merged 3 commits into4.5.2-beta1from
Bug_#911_continue_on_get_l2len_protcol_is_zero

Conversation

@fklassen
Copy link
Copy Markdown
Member

@fklassen fklassen commented Jul 4, 2025

Standards checklist:

  • The PR title is descriptive.
  • The PR doesn't replicate another PR which is already open.
  • I have read the contribution guide and followed all the instructions.
  • The code follows the code style guide detailed in the wiki.
  • The code is mine or it's from somewhere with an MIT-compatible license.
  • The code is efficient, to the best of my ability, and does not waste computer resources.
  • The code is stable and I have tested it myself, to the best of my abilities.
  • If the code introduces new aliases, I provide a valid use case for all plugin users down below.

Changes:

  • do not fail on l2len == 0

Other comments:

...

GabrielGanne and others added 3 commits January 31, 2025 13:49
When fussing, it's possible to simulate the drop of a packet which
causes get_l2len_protocol to see a packet with a l2_len=0

Instead of aborting the whole process, let's just skip the packet.
do not exit in get_l2len_protocol() if l2len==0
@fklassen fklassen added the bug label Jul 4, 2025
@fklassen fklassen merged commit dfd8651 into 4.5.2-beta1 Jul 4, 2025
2 checks passed
@fklassen fklassen deleted the Bug_#911_continue_on_get_l2len_protcol_is_zero branch July 4, 2025 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants