Skip to content

Commit 96a5c3d

Browse files
authored
Capture filter limitations
1 parent 79b14ea commit 96a5c3d

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/defender-for-iot/organizations/cli-ot-sensor.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -617,8 +617,9 @@ The basic use case for capture filters uses the same filter for all Defender for
617617
- `traffic-monitor`: Captures communication statistics
618618

619619
> [!NOTE]
620-
> Capture filters don't apply to [Defender for IoT malware alerts](../alert-engine-messages.md#malware-engine-alerts), which are triggered on all detected network traffic.
620+
> - Capture filters don't apply to [Defender for IoT malware alerts](../alert-engine-messages.md#malware-engine-alerts), which are triggered on all detected network traffic.
621621
>
622+
> - The capture filter command has a limited character length for defining subnet definitions, depending on the hardware limitations in your system.
622623
623624
### Create a basic filter for all components
624625

0 commit comments

Comments
 (0)