is it only IPv6 clients communicate via IPv6 LB to only IPv6 Virtual machines behind that LB and not IPv6 clients to IPv4 VM via IPv6LB
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.
Please support configurable public IPv6 Idle Timeout for feature parity with public IPv4 Idle Timeout3 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_80801 vote
Thank you for your suggestion. We are reviewing it and will get back to you.
- Don't see your idea?