Content deleted Content added
mNo edit summary |
only fixed the table layout. |
||
| (45 intermediate revisions by 19 users not shown) | |||
Line 1:
{{Original research|table|date=July 2022}}
{{Short description|None}}
This is a comparison of applications in regard to their support of the [[IPv6]] protocol.
{|
|-
!
|-
|[[Android Studio]]
|[[Microsoft Windows|Windows]]
|
|{{no}}
|Cannot download [[software development kit|SDK]] components from behind a [[NAT64]], requires native [[IPv4]]
|-
|[[Arduino]] Studio
|Windows
|
|{{
|Cannot download board definitions from behind a NAT64, requires native IPv4
|-
|[[
|Windows
|
|{{no}}
|The [[license server]] only binds to and listens on IPv4
|-
|[[Avigilon|Avigilon Control Center]]
|Windows
|
|{{no}}
|
|-
|[[Bromcom|Bromcom MIS]]
|Windows
|
|{{partial}}
|Bromcom MIS will work on an IPv6 only network, however the [[access-control list]]s do not support IPv6 and have to be removed from a user's account directly in the [[SQL]] [[database]]. Bromcom does not officially support IPv6.
|-
|[[Google Chrome]]
|Windows
|
|{{yes}}
|
|-
|[[Mozilla]] [[Firefox]]
|Windows
|46 (Tested)
|{{yes}}
|Supports [[IPv6 address]]es under Windows using brackets as [IPv6]:port
|-
|[[Microsoft]] [[Internet Explorer]]
|Windows
|11
|{{yes}}
|Supports IPv6 addresses under Windows using brackets as [IPv6]:port
|-
|Windows [[File Explorer]]
|Windows
|Tested with [[Windows 7]]–[[Windows 10|10]], maybe [[Windows XP|XP]]
|{{yes}}
|Supports IPv6 addresses in the address field, using \\fe80--abcd-eff0.ipv6-literal.net using [[dash]]es instead of [[colon (punctuation)|colons]].
|-
|[[Microsoft Exchange Server]]<ref name="auto">{{cite web|url=https://technet.microsoft.com/en-us/network/hh994905.aspx|title=IPv6 Support in Microsoft Products and Services|publisher=Microsoft|accessdate=2015-12-15|archive-url=https://web.archive.org/web/20151222142339/https://technet.microsoft.com/en-us/network/hh994905.aspx|archive-date=2015-12-22|url-status=dead}}</ref>
|Windows
|2013+
|{{yes}}
|
|-
|[[Internet Explorer]]<ref name="auto"/>
|Windows
|9+
|{{yes}}
|
|-
|[[Microsoft SQL Server]]<ref name="auto"/>
|Windows
|2005+
|{{yes}}
|
|-
|Microsoft [[Windows Server Update Services]]<ref name="auto"/>
|Windows
|4.0
|{{yes}}
|WSUS will work in an IPv6 only network, however Microsoft's Windows Update servers are only available over IPv4 so either an [[IPv6 transition mechanism]] will be needed, or a [[proxy server]].
|-
|[[Mosh (software)|Mosh]]
|[[Linux]]
|1.2.5+
|{{Yes}}
|
|-
|[[PuTTY]]
|All
|0.66+
|{{yes}}
|
|-
|[[Sage 200cloud]]
|Windows
|v2015 and v2016
|{{partial}}
|Sage 200 mostly works in an IPv6 environment as it is based on Microsoft [[Internet Information Services|IIS]]. Activation will not work over IPv6 or using a proxy server so the Sage application server needs to have an IPv4 address to activate. The Sage 200 task launch will also fail to run if the IPv6 stack is uninstalled.
|-
|[[Skype for Business]]
|Windows
|All
|{{partial}}
|The [[Skype]] for Business client supports IPv6 only networks where the IPv4 stack is not bound to a network adapter, however it will crash if the IPv4 stack is uninstalled.
|-
|[[Smoothwall]]<br>SWG, UTM and WAM
|Linux
|All
|{{no}}
|
|-
|[[SolarWinds]] [[TFTP]] Server
|Windows
|10+
|{{yes}}
|
|-
|[[SolidWorks|SolidNetwork License Manager]]
|Windows
|All
|{{no}}
|
|-
|[[Spotify]]<br>(Windows [[Universal Windows Platform|UWP]] app)
|Windows
|
|{{no}}
|No network connectivity detected by the app from behind NAT64, requires native IPv4
|-
|[[Steam (service)|Steam Client]]
|Windows,<br>[[macOS]],<br>Linux
|All
|{{no}}
|Cannot log in on IPv6-only network. If logged in on an IPv4 network and moved to an IPv6 network, Steam Client goes offline.<ref>{{cite web|title=Steam doesn't work on IPv6-only (NAT64/DNS64) networks|url=https://github.com/ValveSoftware/steam-for-linux/issues/3372|website=Github|accessdate=2020-10-13}}</ref>
|-
|[[Netflix]] app
|[[LG Electronics|LG]] [[webOS]],<br>[[Xbox system software|Xbox OS]]
|All
|{{no}}
|[[Hardcoded]] to send [[DNS]] requests to 8.8.8.8, or the [[DHCP]]v4 designated DNS server as a fallback if 8.8.8.8 is unreachable. Only requests A records, not AAAA, meaning it is completely dependent on IPv4. LG webOS and other LG webOS applications run fine without IPv4 access, so it is not the fault of the [[operating system]].<ref>{{cite web|title=My LG WebOS Smart TV NAT64 IPv6-only experience (LG OLED CX 65") in Australia|url=https://www.reddit.com/r/ipv6/comments/nal29s/my_lg_webos_smart_tv_nat64_ipv6only_experience_lg|website=Reddit|date=12 May 2021 |accessdate=2021-05-29}}</ref>
|-
|[[Thermomix]]
|Thermomix OS
|All
|{{yes}}
|The Thermomix® TM6 supports the current standard Internet protocol IPv6<ref name="vorwerk">{{cite web |url=https://support.vorwerk.com/hc/en-us/articles/360000895505-Does-the-Thermomix-TM6-support-the-Internet-protocol-IPv6 |title=Does the Thermomix® TM6 support the Internet protocol IPv6? |work= Vorwerk International Help Center THERMOMIX® Thermomix® TM6 Technical specifications |publisher=vorwerk.com |date=2023-12-15 |accessdate=2024-05-23 |quote=TM6 supports the current standard Internet protocol IPv6 }}</ref>
|-
|[[Microsoft Store]]
|[[Xbox]] OS
|All
|{{partial}}
|[[Xbox Series]] X - can browse the store using IPv6-only connection with NAT64, but [[download]]s get stuck in the queue until native IPv4 is available
|}
==References==
{{reflist}}
{{IPv6}}
| |||