--- title: "Configure access rules for fragmented traffic" slug: "configure-access-rules-for-fragmented-traffic-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:31:15Z published: 2026-11-19T12:31:15Z canonical: "docs.trellix.com/configure-access-rules-for-fragmented-traffic-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure access rules for fragmented traffic L3 Firewall access rules allow you to selectively specify rules for a host (or network) based on which Trellix IPS skips reassembly handling of the fragmented traffic. This helps in decreasing the latency of the fragmented traffic for the specified network or host. L3 Firewall access rules do not apply to non-fragmented traffic. It is advisable to use this feature only with a trusted host and only if you are receiving extremely a high amount of fragmented traffic. For example, you could use L3 Firewall access rules if your NFS server is sending a huge amount of fragmented traffic through a Sensor. Note that using this feature while receiving traffic from an unknown host can mean evasion using IP address fragments. In Trellix IPS, the rules that can be set for L3 Firewall access rules are as follows: - *Ignore*: Fragmented traffic that matches the L3 Firewall access rules applied is sent inline without reassembly. - *Scan*: Fragmented traffic that matches the L3 Firewall access rules applied is reassembled prior to IPS processing. - *Drop*: Fragmented traffic that matches the L3 Firewall access rules applied is dropped by the Sensor. All fragmented traffic is reassembled before IPS processing if traffic does not match any L3 ACL rules. In Trellix IPS, three default Service rule objects are provided to support fragmented ICMP, TCP, and UDP. They are ICMP-Fragmented, TCP-Fragmented, and UDP-Fragmented. The user-specified protocol numbers are not supported. From Manager, you can configure the access rules for fragmented traffic. **Steps:** 1. Select **Intrusion Prevention** → **Policy Types** → **Firewall**. 2. Click ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a265d0b5-4039-16f5-7bb1-cb4512697e13(8).png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A44%3A46Z&se=2026-11-20T11%3A44%3A46Z&sr=c&sp=r&sig=HH1P7fwfBHtcSu63ZpCJdMHi4qUzvcw9WTwalz4ArWY%3D). 3. On the **Properties** tab, enter a **Name** and **Description** for the policy. The **Owner** field corresponds to the admin that you selected. 4. In the **Visibility** field, select **Owner and Child Domains**. 5. From the **Type** drop-down, select **Advanced** or **Classic**. 6. Click **Next** to view the **Access Rules** tab. 7. Click the relevant button to insert a new access rule at the appropriate location within the list of access rules. 8. In the **Application** section, select the required option from the list. 9. Select a protocol — ICMP- Fragmented, TCP - Fragmented, or UDP- Fragmented. When L3 Firewall Access Rules are configured, set **TCP Flow Violation** to **Permit out-of-order** (the default setting). 1. Click the **Devices** tab. 2. Select the domain from the **Domain** drop-down list. 3. In the left pane, click the **Devices** tab. 4. Select the device from the **Device** drop-down list. 5. Select **Setup** → **Advanced** → **Protocol Settings**. 6. In the **Protocol Settings** page, from the **TCP Flow Violation** drop-down list, select **Permit out-of-order**. 7. Click **Update** that corresponds to **TCP Flow Violation**.