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: memdocs/intune/protect/microsoft-tunnel-prerequisites.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -341,19 +341,19 @@ For more information about this tool, see [Reference for mst-cli](../protect/mic
341
341
342
342
### Manually load ip_tables
343
343
344
-
While most Linux distributions include the ip_tables module, some distributions might not. For example, REHL 8.5 doesn't load the ip_tables by default.
344
+
While most Linux distributions automatically load the ip_tables module, some distributions might not. For example, REHL 8.5 doesn't load the ip_tables by default.
345
345
346
-
To check for the presence of this module, run the most recent version of mst-readiness tool on the server to validate its presence. The check for ip_tables was added to the readiness tools script on February 11 2022.
346
+
To check for the presence of this module, run the most recent version of mst-readiness tool on the Linux server. The check for ip_tables was added to the readiness tools script on February 11 2022.
347
347
348
-
If the module isn’t present, the tool will stop on the ip_tables module check. In this scenario, you can run the following commands to manually load the ip_tables module, and then validate they're now present.
348
+
If the module isn’t present, the tool stops on the ip_tables module check. In this scenario, you can run the following commands to manually load the module.
349
349
350
350
**Manually load the ip_tables module**:
351
351
352
-
In the context of sudo, run the following commands on your Linux server to validate the presence of the tables, and then to manually load them if necessary:
352
+
In the context of sudo, run the following commands on your Linux server:
353
353
354
354
1. Validate the presence of ip_tables on the server: `lsmod |grep ip_tables`
355
355
356
-
2. If ip_tables isn't present, run the following to load the module into the kernel immediately, without a restart: Run `/sbin/modprobe ip_tables`
356
+
2. If ip_tables isn't present, run the following to load the module into the kernel immediately, without a restart: `/sbin/modprobe ip_tables`
357
357
358
358
3. Rerun the validation to confirm the tables are now loaded: `lsmod |grep ip_tables`
0 commit comments