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 https://github.com/Azure/iotedge/blob/main/doc/IPv6Configuration.md. For me, this worked only for the default bridge network but not for the "azure-iot-edge" network. I also checked the https://github.com/Azure/iotedge/blob/1.5.16/doc/networking.md 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.
windows server rras record other C/S address in SSTP tunnel over ipv6
We can see that Client/Server ipv6 addresses in RRAS MMC console are not the same with netstat log. In rras SSTP mode, client connect to server port 443/tcp. Using packet capture tool such as wireshark, I found netstat tells the right address. Why RRAS mmc console print strange C/S addresses, with the same ipv6 prefix /64 as the netstat answer. Radius auth/accounting records are the same with rras mmc console. The same problem found in windows server 2016. When switch to IKEv2 tunnel mode, addresses in MMC are the same with netstat. The problem was not found in ipv4 tunnel. DirectAccess feature is not enable. Is this C/S addresses transform a feature? What for? Maybe Directaccess?
Small Business Server 2011 Slow to Boot and Several Services Fail to Start
First published on TechNet on Feb 18, 2011 [Today's post comes to us courtesy of Justin Crosby and Shawn Sullivan from Commercial Technical Support]If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2011 server you may see the following issues after a reboot:Microsoft Exchange services fail to start Server hangs at "Applying Computer Settings.Issues After Disabling IPv6 on Your NIC on SBS 2008
First published on TechNet on Oct 24, 2008 [Today's post comes to us courtesy of Justin Crosby, Ed Walters, and Doug Boyd]If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:Microsoft Exchange services fail to start Server hangs at "Applying Computer Settings.
