Trying to access another device from the host network from the IoT Edge modules about azure-iot-edge

[DirkMeihoefer]

We did not tried this scenario ourself. My first idea and quick shot would be to create and configure an azure-iot-edge docker network to use the macvlan driver if that would be acceptable. Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. This network can be configured before starting IoT Edge, as the iotedged does a "get or create" operation on the network when starting. Pre-configuring a network and updating the network in the config.yaml allows complete control over its settings.
Networking on IoT Edge

[IkkertSergei]

Hello bosman84 . The solution described by colleague Dirk is based on the case that the external devices should access the Iot-Edge modules. In this case Macvlan approach makes sense.
In the case that the Iot-Edge modules should communicate with an external device in the same network, it should work without any problems. I have already tried Azure IoT Edge Modbus modules and it worked once.
https://github.com/Azure/iot-edge-modbus
We are currently working on the new version of Iot Edge runtime. This will be the last released version 1.0.10 of iot edge where some bugs have been fixed. The version will probably be released next week on docker hub. We will check the communication between Iot-Edge modules and external devices again.

[sbosman84]

Thanks DirkMeihoefer & IkkertSergei, I also expected that it should work on the default bridge network configuration of the azure-iot-edge network. So I've looked into it a bit deeper and think the problem lies in that it is specific to the UDP broadcast that is not being routed proper from the azure-iot-edge network towards the external devices (and back). When running on the host network this isn't a issue. So will need to look into this a bit deeper. Thanks for the support.