Networking
The Networking forum covers all aspects of Networking in Azure, including endpoints, load-balancing, network security, DNS, Traffic Manager, virtual networks, and external connectivity.
Virtual Network:
Traffic Manager:
Network Watcher:
If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.
-
8 votes
The suggestion seems to be a question about IPv6 clients accessing an IPv4-only VM. In Azure, IPv6 traffic from the internet is plumbed directly to native IPv6 endpoints on VMs. There are many advantages to this approach but one disadvantage is the VMs must have IPv6 endpoints and the applications must be IPv6-aware. In the example below, I would guess the web server has not been configured to monitor both the IPv4 and IPv6 endpoints on the VM but that is really a support question.
It is possible to translate between IPv4 and IPv6 (NAT64) which is not currently supported in Azure so we’ll take this suggestion as a vote for NAT64 support. -
3 votes
thank you for the suggestion. investigating.
-
add support of '--idle-timeout' for "az network lb rule update -g lwm2m6 --lb-name lblwm2m6 --idle-timeout 30 -n IPv6Tcp80_8080"
Want to configure '--idle-timeout':
az network lb rule update -g lwm2m6 --lb-name lblwm2m6 --idle-timeout 30 -n IPv6Tcp80_8080
1 voteThank you for your suggestion. We are reviewing it and will get back to you.
- Don't see your idea?