Dropped packets because of "Invalid TCP Flag"

12/20/2019 360 29825

DESCRIPTION:

This article describes how to workaround the drop "(Invalid TCP Flag(#2)), Module Id: 25(network)" due to network issues.

CAUSE:

• Packets may be perceived as having Invalid TCP flag if packets with SYN+ACK+PSH, instead of SYN+ACK, are received.
• Packets may get to the SonicWall with incorrect sequence numbers due to 3rd party issues or source configuration (i.e. sequence number randomization).

RESOLUTION:

Here's some workarounds for this issue.

 NOTE: Invalid TCP Flag drops are usually related to a 3rd party issue as the packets are arriving to the SonicWall with a wrong sequence number or in wrong order.

• Enable Fix/ignore malformed TCP headers and disable Enable TCP sequence number randomization in the internal settings page.
  1. Enter the internal settings page by entering diag.html in the address bar in place of main.html.
  2. Click on Internal Settings.
     

     

     

  3. Enable Fix/ignore malformed TCP headers and disable Enable TCP sequence number randomization.
     

• If the drop is related to incorrect sequence number, you might disable Enforce strict TCP compliance with RFC 793 and RFC 1122 from Firewall Settings | Flood Protection but this could cause security breaches.

Resolution for SonicOS 6.2 and Below

The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.

Here's some workarounds for this issue.

NOTE: Invalid TCP Flag drops are usually related to a 3rd party issue as the packets are arriving to the SonicWall with a wrong sequence number or in wrong order.

• Enable “Fix/ignore malformed TCP headers“ and disable “Enable TCP sequence number randomization” in the internal settings page.
  1. Enter the internal settings page by entering diag.html in the address bar in place of main.html.
  2. Click Internal Settings.
     

     

     

  3. Enable Fix/ignore malformed TCP headers and disable Enable TCP sequence number randomization. 

• If the drop is related to incorrect sequence number, you might disable Enforce strict TCP compliance with RFC 793 and RFC 1122 from Firewall Settings | Flood Protection but this could cause security breaches.