Comparison of IPv6 support in common applications: Difference between revisions

Revision as of 10:31, 29 June 2021

Latest revision as of 07:17, 19 March 2025

(7 intermediate revisions by 6 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.

{| class="wikitable sortable" style="font-size: 85%;"text-align:center

|-

! Application !! OS !! Version !! IPv6 Support || !!Notes

|-

|[[Android Studio]]

|AB Tutor

|[[Microsoft Windows|Windows]]

|7+

|{{yes}}

|

|-

|Android Studio

|Windows

|

|{{no}}

| Cannot download [[software development kit|SDK]] components from behind a [[NAT64]], requires native [[IPv4]]

|-

|[[Arduino]] Studio

|Windows

|

|{{no}}

| Cannot download board definitions from behind a NAT64, requires native IPv4

|-

|[[Sibelius Software(scorewriter)|Avid Sibelius License Server]]

|Windows

|allAll

|{{no}}

| The [[license server]] only binds to and listens on IPv4

|-

|[[Avigilon|Avigilon Control Center]]

|Windows

|allAll

|{{no}}

|Neither the server, client ornor cameras[[camera]]s support IPv6

|-

|[[Bromcom|Bromcom MIS]]

|Windows

|allAll

|{{partial}}

|Bromcom MIS will work on an IPv6 only network, however the Access[[access-control Control Listslist]]s do not support IPv6 and have to be removed from a usersuser's account directly in the [[SQL]] [[database]]. Bromcom dodoes not officially support IPv6.

|-

|[[Google Chrome]]

Line 47 ⟶ 43:

|

|-

|[[Mozilla]] [[Firefox]]

|Windows

|46 (Tested)

|46tested

|{{yes}}

|Supports [[IPv6 addressesaddress]]es under Windows using brackets as [IPv6]:port

|-

|[[Microsoft]] [[Internet Explorer]]

|Windows

|11

Line 59 ⟶ 55:

|Supports IPv6 addresses under Windows using brackets as [IPv6]:port

|-

|Windows [[File Explorer]]

|Windows

|testedTested with Win[[Windows 7–107]]–[[Windows 10|10]], maybe [[Windows XP|XP]]

|{{yes}}

|Supports IPv6 addresses in the address field, using \\fe80--abcd-eff0.ipv6-literal.net using dashes[[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>

Line 83 ⟶ 79:

|

|-

|Microsoft [[Windows Server Update Services|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_Mosh (software)|Mosh]]

|[[Linux]]

|1.2.5+

|{{Yes}}

|-

|[[PaperCut]]

|Windows

|all

|{{partial}}

|The PaperCut 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. The PaperCut printer port does not support IPv6.

|-

|Planet eStream

|Windows

|test v6.10.05.10+

|{{partial}}

|The bulk of Planet eStream works perfectly over IPv6. The main feature that doesn't work is streaming video. Video playback will fall back to HTTP over IPv6 and you can't live stream from the encoder application, although it will upload recorded videos (a special IPv6 build of the encoder was provided / unsure if this is generally available at the moment). You also can't stream live TV over IPv6.

|-

|[[PuTTY]]

|allAll

|0.66+

|{{yes}}

|

|-

|[[Sage_Group | Sage 200200cloud]]

|Windows

|v2015 and v2016

|{{partial}}

|Sage 200 mostly works in an IPv6 environment as it's 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 (Sage 200 offline activation has to be redone every 30 days!). The Sage 200 task launch will also fail to run if the IPv6 stack is uninstalled.

|-

|[[Skype for Business]]

|Windows

|allAll

|{{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|Smoothwall ]]<br>SWG, UTM and WAM]]

|Linux

|allAll

|{{no}}

|

|-

|[[SolarWinds]] [[TFTP]] Server

|Windows

|10+

Line 138 ⟶ 123:

|[[SolidWorks|SolidNetwork License Manager]]

|Windows

|allAll

|{{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, OSX<br>[[macOS]], <br>Linux

|allAll

|{{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]]

|LG WebOS, Xbox OS

|allAll

|{{no}}

|[[Hardcoded]] to send [[DNS]] requests to 8.8.8.8, or the DHCPv4[[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 WebOSwebOS and other LG WebOSwebOS 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

|allAll

|{{noyes}}

|HangsThe ifThermomix® connectingTM6 tosupports NAT64the Wi-Ficurrent network;standard noInternet connectivity.protocol IPv6<ref name="vorwerk">{{cite web |title=Does the Thermomix TM6 support the Internet protocol IPv6? - Vorwerk International Help Center |url=https://support.vorwerk.com/hc/en-us/articles/360000895505-Does-the-Thermomix-TM6-support-the-Internet-protocol-IPv6- |websitetitle=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=20212024-0605-0423 |quote=TM6 supports the current standard Internet protocol IPv6 }}</ref>

|-

|[[Microsoft Store]]

|[[Xbox]] OS

|allAll

|{{partial}}

|[[Xbox Series]] X - can browse the store using IPv6-only connection with NAT64, but downloads[[download]]s get stuck in the queue until native IPv4 is available

|-

|}

== References ==

{{reflist}}

<references />

{{IPv6}}