Special considerations for Linux modules on Windows devices

Exposing services externally on Windows devices

For Linux modules hosted on Windows devices, the module's ports are not automatically exposed by the host device. Port forwarding enables external access to Linux modules hosted on a Windows device by redirecting communication from a specific port on the host device to a port on the module.

To expose a module port to the external network, run the following command in an administrative command prompt on the Windows device:

netsh interface portproxy add v4tov4 listenport=<port> connectaddress=%AVEVALocalEdgeVM% connectport=<port>

After running this command, incoming requests received by the device on the listenport are mapped to connectport on the module, enabling external access to the module.

For example, a Linux module is hosted on a Windows device, and is listening for requests on port 12345. There is a firewall rule in place that allows the Windows device to accept requests on port 12390. After running the following command, requests received on port 12390 by the Windows device are forwarded to port 12345, allowing the module to respond to the requests:

netsh interface portproxy add v4tov4 listenport=12390 connectaddress=%AVEVALocalEdgeVM% connectport=12345

Choosing custom DNS servers for Linux modules on Windows devices

When hosting a Linux module on a Windows device, the bootstrapping process creates a Linux virtual machine on the device to sandbox Linux modules. This virtual machine will use the DNS server 1.1.1.1 by default, but if this DNS server cannot be reached during the bootstrapping process, the DNS configuration from the host Windows device is used instead.

Configure a custom DNS server

1. On the Windows device, open the PowerShell CLI in administrator mode.

2. Test your chosen DNS server by attempting to resolve google.com with the following command, replacing 1.2.3.4 with the address of your DNS server:

   Resolve-DnsName -Name google.com -Server "1.2.3.4"

   If no errors occur and the IP address for google.com is displayed, continue to the next step.

3. Configure the DNS server that will be used by Linux modules using the following command:

   Set-EflowVmDNSServers -dnsServers @(<DNS Server address>)

   To configure a primary and secondary DNS server, you can comma-separate multiple addresses.

   For example, this command sets 1.1.1.1 as the DNS server:

   Set-EflowVmDNSServers -dnsServers @("1.1.1.1")

   This command sets 1.1.1.1 and 8.8.8.8 as the primary and secondary DNS servers:

   Set-EflowVmDNSServers -dnsServers @("1.1.1.1","8.8.8.8")