--- title: "Configure and manage packet capture rules" slug: "configure-and-manage-packet-capture-rules-3" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:28:23Z published: 2026-11-19T12:28:23Z canonical: "docs.trellix.com/configure-and-manage-packet-capture-rules-3" --- > ## 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 and manage packet capture rules You can filter the rule for capturing packets and apply it as a packet capture profile. 1. For a standalone Sensor, go to **Devices** → **** → **Devices** → **** → **Troubleshooting** → **Packet Capturing** → **Capture Now**. For Sensors in a stack, go to **Devices** → **** → **Devices** → **** → **Member Sensors** → **** → **Troubleshooting** → **Packet Capturing** → **Capture Now**. For member Sensors in a cluster, go to **Devices** → **** → **Devices** → **** → **Member Sensors** → **** → **Troubleshooting** → **Packet Capturing** → **Capture Now**. 2. Under **Capture Rules**, the following list of capture rules is displayed. | Option | Definitions | | --- | --- | | **Monitoring port** | The monitoring ports on which the rule is applied: The options are: **All** and ****. > [!NOTE] > Note > > Some options may not be displayed, depending on the configured Sensor model. | | **Traffic** | The traffic for which the capture rule is to be filtered. The options are: **ALL**, **ARP** and **IP**. | | **Protocol** | Type of protocols to be filtered. The options are: **TCP**, **UDP**, **ICMP**, and **Protocol Number**. | | **IP Version** | Type of IP setting: - For **ALL** and **ARP** traffic, IP setting (**IPv4**) - For **IP** traffic, IP setting (**IPv4**/**IPv6**) | | **Fragments Only?** | Captures only the fragmented traffic. By default this option is disabled. | | **Source IP** | Source IP address of the packet | | **Source Mask** | Source IP mask | | **Source Port** | Source port number of the packet. This option will be enabled only if you select the protocol type as **TCP** or **UDP**. | | **Destination IP** | Destination IP address of the packet | | **Destination Mask** | Destination IP mask | | **Destination Port** | Destination port number of the packet. This option will be enabled only if you select the protocol type as **TCP** or **UDP** | | **Vlan ID** | VLAN ID of the packet to be captured. This option will be disabled if you select the protocol type as **ALL** or **ARP**. > [!NOTE] > Note > > Only the outer VLAN ID will be inspected in case of double VLAN tagged traffic | | **Protocol Number** | The protocol number. This can be specified only if the option **Protocol Number** is selected under **Protocol**. | - When a packet capture session is in progress, you cannot configure/push a new packet capture profile. To apply a new profile, the packet capture session needs to be stopped. - You can add/remove the rows by clicking **-** or **+** signs on the right-hand side of the **Capture Rules** field. 3. The Capture Rule Template can be defined at the admin level to be applied across multiple Sensors or at a Sensor level. - To create a packet capture rule template at an admin-domain level, select **Policy** → **** → **Intrusion Prevention** → **Objects** → **Packet Capture Rule Templates** → **New**. - To create a packet capture rule template at a standalone Sensor level, select **Devices** → **** → **Devices** → **** → **Troubleshooting** → **Packet Capturing** → **Capture Now** → **Insert Capture Rule Template** → **New**. - To create a packet capture rule template at a Sensor in a stack, select **Devices** → **** → **Devices** → **** → **Member Sensors** → **** → **Troubleshooting** → **Packet Capturing** → **Capture Now** → **Insert Capture Rule Template** → **New**. The **Add a Capture Rule Template** page opens. **Add a Capture Rule Template window**![Add a Capture Rule Template window](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-c2f84181-4e46-4a96-24fd-97731c7ef4fa(7).png?sv=2026-02-06&spr=https&st=2026-11-20T08%3A03%3A58Z&se=2026-11-20T09%3A03%3A58Z&sr=c&sp=r&sig=6q1Pq8yU26FC98WEWsBUduPMSo5YXZpUqxE7W9FKyLo%3D) 4. Type the **Name** of the capture rule. 5. Select the **Make Visible to Child Admin Domains?** option to make the rule visible to the child admin domain. 6. Click **Save** to save the capture rule. 7. The capture rules can be modified. Once a rule is modified, click **Save**. 8. To delete a capture rule, click ![GUID-9A719AD5-F6BE-4CD4-9311-CC6655DF9B70-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-87ec782a-bd04-c966-9825-e6502cbd0a73(7).png?sv=2026-02-06&spr=https&st=2026-11-20T08%3A03%3A58Z&se=2026-11-20T09%3A03%3A58Z&sr=c&sp=r&sig=6q1Pq8yU26FC98WEWsBUduPMSo5YXZpUqxE7W9FKyLo%3D) against the rule. Click **Save**. > [!NOTE] > Note > > A modification of the template rule does not affect the rule of the Sensor on which it has been applied.