You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/cli-ot-sensor.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -617,8 +617,9 @@ The basic use case for capture filters uses the same filter for all Defender for
617
617
- `traffic-monitor`: Captures communication statistics
618
618
619
619
> [!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.
621
621
>
622
+
> - The capture filter command has a limited character length for defining subnet definitions, depending on the hardware limitations in your system.
0 commit comments