#Microsoft edge for linux how to#

You'll choose which one of each you want when you create it previous to EFLOW deployment.

Virtual switch choicesĮFLOW supports two types of Hyper-V virtual switches: internal and external. To handle different types of networking, you can use different types of virtual switches and add multiple virtual network adapters. However, there's a comprehensive guide on Azure IoT Edge for Linux on Windows virtual switch creation. On Windows Server SKUs devices, networking is a bit more complicated as there's no default switch available. During EFLOW deployment, if no specific virtual switch is specified using the -vSwitchName and -vSwitchType flags, the virtual machine will be created using the default switch. The easiest way to establish basic networking on Windows client SKUs is by using the default switch already created by the Hyper-V feature. Basic networking in EFLOW is simple it uses two parts, a virtual switch and a virtual network. For more information about Hyper-V networking, see Hyper-V networking basics. To establish a communication channel between the Windows host OS and the EFLOW virtual machine, we use Hyper-V networking stack.

For more information about EFLOW architecture, see What is Azure IoT Edge for Linux on Windows. EFLOW uses a CBL-Mariner Linux virtual machine in order to run IoT Edge modules.

#Microsoft edge for linux how to#

This article provides information about how to configure the networking between the Windows host OS and the IoT Edge for Linux on Windows (EFLOW) virtual machine. Applies to: IoT Edge 1.1 IoT Edge 1.2 IoT Edge 1.3 IoT Edge 1.4