Skip to content

Commit e6aee2d

Browse files
authored
Merge pull request #291991 from tarTech23/dhcp
DHCP ranges
2 parents 98cf29f + 608d507 commit e6aee2d

File tree

2 files changed

+18
-4
lines changed

2 files changed

+18
-4
lines changed

articles/defender-for-iot/organizations/configure-sensor-settings-portal.md

Lines changed: 18 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Your new setting is now listed on the **Sensor settings (Preview)** page under i
5454

5555
> [!TIP]
5656
> You may want to configure exceptions to your settings for a specific OT sensor or zone. In such cases, create an extra setting for the exception.
57-
>
57+
>
5858
> Settings override each other in a hierarchical manner, so that if your setting is applied to a specific OT sensor, it overrides any related settings that are applied to the entire zone or site. To create an exception for an entire zone, add a setting for that zone to override any related settings applied to the entire site.
5959
>
6060
@@ -120,6 +120,7 @@ The **Type** settings are:
120120
- [Local subnets](#local-subnets)
121121
- [VLAN naming](#vlan-naming)
122122
- [Public addresses](#public-addresses)
123+
- [DHCP ranges](#dhcp-ranges)
123124

124125
To add a new setting **Type**, select **Sites and sensors** > **Sensor settings**. Select the setting from the **Type** drop down, for example:
125126

@@ -186,18 +187,31 @@ Select **Add VLAN** to add more VLANs as needed.
186187

187188
### Public addresses
188189

189-
Add public addresses that might have been used for internal use and shouldn't be included as suspicious IP addresses or tracking the data<!-- Theo is this correct? OR-->.
190-
Excluded public IP addresses that might have been used for internal use and shouldn't be included as suspicious IP addresses or tracking the data.
190+
Add public addresses that might have been used for internal use and shouldn't be included as suspicious IP addresses or tracking the data.
191191

192192
1. In the **Settings** tab, type the **IP address** and **Mask** address.
193193

194194
:::image type="content" source="media/configure-sensor-settings-portal/sensor-settings-ip-addresses.png" alt-text="The screenshot shows the Settings tab for adding public addresses to the sensor settings.":::
195195

196-
1. Select **Next**.
196+
1. Select **Next**
197197
1. In the **Apply** tab, select sites, and toggle the **Add selection by specific zone/sensor** to optionally apply the IP addresses to specific zones and sensors.
198198
1. Select **Next**.
199199
1. Review the details and select **Create** to add the address to the public addresses list.
200200

201+
### DHCP ranges
202+
203+
Add the range of IP addresses to configure the DHCP settings that can apply to a device that might have multiple IP addresses associated with it.
204+
205+
1. In the **Settings** tab, type the **From** and **To** IP addresses, and optionally enter a **Name**.
206+
207+
:::image type="content" source="media/configure-sensor-settings-portal/dhcp-ranges.png" alt-text="The screenshot shows the Settings tab for adding DHCP IP addresses to the sensor settings.":::
208+
209+
1. To add additional ranges, select **Add range**.
210+
1. Select **Next: Selection**.
211+
1. In the **Apply to** tab, select the sites, and toggle the **Add selection by specific zone/sensor** to optionally apply the IP addresses to specific zones and sensors.
212+
1. Select **Next: Review**.
213+
1. Review the details and select **Save and assign** to add the range of addresses to the DHCP range list.
214+
201215
## Next steps
202216

203217
> [!div class="nextstepaction"]
43.6 KB
Loading

0 commit comments

Comments
 (0)