You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arduino IDE cannot download board definitions on IPv6-only network (NAT64 / DNS64) on Windows. I will test Linux when I have more time and will update you on Linux. This IPv6-only network works for all applications which support proper networking API calls. It provides access to IPv4 services by synthesising an AAAA record for all domain names without one, and then using the NAT64 to exchange IPv6 <-> IPv4 packets on the network boundary. If I move it onto a different network segment with dual-stack IPv4 / IPv6, then the downloads work using native IPv4.
This can be for a couple of reasons:
IPv4 hardcoded literals will fail on IPv6-only network - should always use DNS to resolve addresses
Legacy networking API calls which cannot handle any address family
This is a ticking time bomb, as IPv6 adoption grows. https://www.google.com/intl/en/ipv6/statistics.html
ISPs which offer IPv6-only will grow from being rare to becoming common. You will alienate these users, and for what? Holding onto legacy API calls?
Please strongly consider testing the Arduino IDE out on an IPv6-only network, and fix any issues which arise from network connectivity.
You can get an IPv6-only network with which to test:
Get a dual-stack IPv4 / IPv6 connection (very common, particularly on cellular networks), disable IPv4 in the network adapter, and set the IPv6 DNS to one of the server addresses obtained from https://nat64.net/
Thank you!
The text was updated successfully, but these errors were encountered:
Arduino IDE cannot download board definitions on IPv6-only network (NAT64 / DNS64) on Windows. I will test Linux when I have more time and will update you on Linux. This IPv6-only network works for all applications which support proper networking API calls. It provides access to IPv4 services by synthesising an AAAA record for all domain names without one, and then using the NAT64 to exchange IPv6 <-> IPv4 packets on the network boundary. If I move it onto a different network segment with dual-stack IPv4 / IPv6, then the downloads work using native IPv4.
This can be for a couple of reasons:
This is a ticking time bomb, as IPv6 adoption grows. https://www.google.com/intl/en/ipv6/statistics.html
ISPs which offer IPv6-only will grow from being rare to becoming common. You will alienate these users, and for what? Holding onto legacy API calls?
Please strongly consider testing the Arduino IDE out on an IPv6-only network, and fix any issues which arise from network connectivity.
You can get an IPv6-only network with which to test:
Thank you!
The text was updated successfully, but these errors were encountered: