Document Details
How To Configure Multiple Nics
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
windows_first
⚠️
missing_linux_example
Summary:
The documentation is heavily focused on Windows and PowerShell tooling for configuring multiple NICs on Azure IoT Edge for Linux on Windows (EFLOW). All configuration steps are performed using PowerShell commands and Windows-specific tools, with no equivalent Linux command-line or cross-platform alternatives provided. The workflow assumes the user is operating from a Windows environment, and Linux-native methods or tools are not mentioned or demonstrated.
Recommendations:
- Provide equivalent Linux command-line examples (e.g., using SSH, nmcli, ip, or netplan) for managing network interfaces inside the EFLOW VM.
- Document how to perform these configuration steps from a Linux or cross-platform environment, if possible.
- Clarify which steps must be performed on the Windows host versus inside the Linux VM, and provide Linux-native alternatives for in-VM configuration.
- Consider including Azure CLI or portal-based instructions where possible to reduce reliance on Windows-specific tools.
- Explicitly state if certain operations are only possible from Windows, and suggest workarounds or alternatives for Linux users.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-09-16 00:00 | #113 | completed | ✅ Clean |
| 2025-09-15 00:00 | #112 | completed | ✅ Clean |
| 2025-09-14 00:00 | #111 | completed | ✅ Clean |
| 2025-09-13 00:00 | #110 | completed | ✅ Clean |
| 2025-09-12 00:00 | #109 | completed | ✅ Clean |
| 2025-09-11 00:00 | #108 | completed | ✅ Clean |
| 2025-09-10 00:00 | #107 | completed | ✅ Clean |
| 2025-09-09 00:00 | #106 | completed | ✅ Clean |
| 2025-09-08 00:00 | #105 | completed | ✅ Clean |
| 2025-09-07 00:00 | #104 | completed | ✅ Clean |
| 2025-09-06 00:00 | #103 | completed | ✅ Clean |
| 2025-09-05 00:00 | #102 | completed | ✅ Clean |
| 2025-09-04 00:00 | #101 | completed | ✅ Clean |
| 2025-09-03 00:00 | #100 | completed | ✅ Clean |
| 2025-08-29 00:01 | #95 | completed | ✅ Clean |
| 2025-08-27 00:01 | #93 | in_progress | ✅ Clean |
| 2025-08-26 00:00 | #92 | in_progress | ✅ Clean |
| 2025-08-22 00:01 | #88 | completed | ✅ Clean |
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ❌ Biased |
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
Add-EflowNetwork -vSwitchName "{switchName}" -vSwitchType {switchType}
Add-EflowNetwork -vSwitchName "OnlineExt" -vSwitchType "External"
Add-EflowVmEndpoint -vSwitchName "{switchName}" -vEndpointName "{EndpointName}"
Add-EflowVmEndpoint -vSwitchName "OnlineExt" -vEndpointName "OnlineEndpoint" -ip4Address "192.168.0.103" -ip4GatewayAddress "192.168.0.1" -ip4PrefixLength "24"
Connect-EflowVm