Content deleted Content added
m →Transport Relay Translation: Typo fixing, replaced: addres → address |
|||
Line 27:
The address, for example, if packets are to be transmitted from an IPv6 address ({{IPaddr|fec0:0:0:1::|64}}) to an IPv4 address ({{IPaddr|10.1.1.1}}) would read as {{IPaddr|fec0:0:0:1::10.1.1.1}}. The packets are routed towards the translator firstly through an IPv6/TCP protocol and then from the translator to the IPv4 host through an IPv4/TCP protocol.<ref>{{cite web |last1=Shanmugaraja |first1=P. |title=Design and Implementation of Transport Relay Translator and its security Mitigations |url=https://www.researchgate.net/publication/290350020 |website=researchgate.net |publisher=Research Gate |access-date=28 June 2024}}</ref>
TRT employs a similar operation to DNS translation between AAAA and A records known as ''[[
==NAT64==
{{main
[[Image:NAT64.svg|thumb|NAT64 and DNS64]]
[[NAT64]] is a mechanism to allow IPv6 hosts to communicate with IPv4 servers. The NAT64 server is the endpoint for at least one IPv4 address and an IPv6 network segment of 32-bits, e.g., {{IPaddr|64:ff9b::|96}}.{{Ref RFC|6052}} The IPv6 client embeds the IPv4 address with which it wishes to communicate using these bits, and sends its packets to the resulting address. The NAT64 server then creates a [[Network address translation|NAT]]-mapping between the IPv6 and the IPv4 address, allowing them to communicate.{{Ref RFC|6146}}
Line 80:
|access-date=5 November 2018|url=https://www.ietf.org/mail-archive/web/v6ops/current/msg30153.html}}</ref> Additionally, Apple requires all apps submitted to the [[App Store (iOS)|App Store]] to work on IPv6 networks.<ref>{{cite web|last1=van Beijnum|first1=Iljitsch|title=Apple to iOS devs: IPv6-only cell service is coming soon, get your apps ready|url=https://arstechnica.com/apple/2015/06/apple-to-ios-devs-ipv6-only-cell-service-is-coming-soon-get-your-apps-ready/|website=Ars Technica|access-date=2 July 2016|date=2015-06-16|archive-date=2016-06-28|archive-url=https://web.archive.org/web/20160628114602/http://arstechnica.com/apple/2015/06/apple-to-ios-devs-ipv6-only-cell-service-is-coming-soon-get-your-apps-ready/|url-status=live}}</ref>
* clatd is a CLAT implementation for [[Linux]].<ref>{{Cite web |last1=Anderson |first1=Tore |date=May 20, 2019 |title=clatd |url=https://github.com/toreanderson/clatd |access-date=January 15, 2023 |website=[[GitHub]] |archive-date=December 17, 2022 |archive-url=https://web.archive.org/web/20221217201141/https://github.com/toreanderson/clatd |url-status=live }}</ref>
* [[Network Manager]] (WIP):<ref>{{Cite web |last1=Strodlr|first1=Mary|date=Jan 12, 2025 |title=Add support for CLAT using a BPF program|url=https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107 |access-date=February 6, 2025 |website=[[GitLab]]|url-status=live}}</ref>
* [[OpenWRT]] linux OS for routers has optional support for clat via the 464xlat package <ref>{{cite web| title=OpenWrt Wiki package: 464xlat|url=https://openwrt.org/packages/pkgdata/464xlat|website=OpenWrt|access-date=1 April 2024}}</ref>
* [[FreeBSD]] has implemented NAT64 CLAT since Release 12.1.<ref>{{Cite web |last=Baoi |first=Danilo G. |date=June 19, 2021 |title=FreeBSD 12.1-RELEASE Release Notes |url=https://www.freebsd.org/releases/12.1R/relnotes/ |website=FreeBSD |access-date=January 15, 2023 |archive-date=January 15, 2023 |archive-url=https://web.archive.org/web/20230115224443/https://www.freebsd.org/releases/12.1R/relnotes/ |url-status=live }}</ref>
| |||