Enable ipv6 for azure-iot-edge user-defined network
We have a Raspberry Pi that we use as an edge device. One of our modules needs to communicate over IPv6 in the local network. Since the module is automatically connected to the "azure-iot-edge" network in Docker, I'd like a method to easily enable IPv6 on this network. To achieve this, I tried following the steps described in the IPv6Configuration documentation. For me, this worked only for the default bridge network but not for the "azure-iot-edge" network. I also checked the networking documentation and attempted to configure the network using the mentioned /etc/aziot/edged/config.yaml file. However, this file did not exist initially, and when I manually added it, it seemed to be completely ignored. The only way I have been able to get IPv6 to work for the "azure-iot-edge" network so far is by completely removing it and manually recreating it with IPv6 enabled. This also required me to manually disconnect and later reconnect all modules. This does not feel like the correct way to achieve this. I would assume there should be a way to configure this either from the module definition in the IoT Hub or by adding some configuration on the device..NET Core Quicksstarts Done quickly with one PowerShell script start to finish.
I have a long time felt that the .NET Core C# Quickstarts for the Azure IoT Hub SDK could be simpler for a newbie. To that end I created the UWP apps Azure IoT Hub Device Streaming and then Azure IoT Hub Toolbox., as available on GitHub and in The Store. These encapsulated the Quickstart functionality and orchestrated IoT Hub creation. This latest salvo into this area can make it even simpler! You run one PowerShell script with which you can create an IoT Hub, get all of the connection strings, save them to environment variables, create PowerShell and Bash scripts to re-set those variables, get the required targeted .NET Core SK binary including expansion of the download amongst other things. Included is a copy of the Quickstarts modified so that all apps get the required connection strings from the environment variables. A couple of variants to the apps have been added. More coming, especially with RPi hardware use. The PowerShell script and its underlying scripts is available on GitHub as Azure IoT Hub PowerShell Scripts . It is a menu driven UI, with a bit of color included!. I have written as series of blogs on .NET Core, especially on the RaspberryPi (IoT-Core and Raspian) and upon running the Quickstarts there via the PowerShell script on my blog at http://www.sportronics.com.au .Here are the specific links: (Note: In reverse order) Remote Publishing to the RPI One more way of doing this - Background Using the PS Script to run Quickstarts on RPi (Raspian) Using the PS Script to run Quickstarts on RPi (IoT-Core) - Simpler Using the PS Script to run Quickstarts on RPi (IoT-Core) Az-IoTHub-PS ... The IoT Hub Quickstart Apps Use the PS Script to set up .NET Core Fast tracking IoT Hub Creation with PS On Windows Subsystem for Linux Getting started on Raspbian Getting started on Win 10 IoT Core Options for the RPi Some key facts Quickstart Apps Overview Extra: Using the az-iothub-ps script Also a presentation on .NET Core on the RPI (the PPT slide deck)
