I see that lemmy.ml is the only major instance currently reachable over IPv6. When will lemmy.world join the modern internet?
this post was submitted on 12 Jun 2023
204 points (100.0% liked)
Lemmy.World Announcements
29018 readers
12 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why does it matter? Actually curious.
My ISP screwed something up last month and no one in my county got an IPv4 address / route for close to 6 hours. Meanwhile, IPv6 worked flawlessly.
Would you not still be able to reach a website over IPv4 even if your IP is IPv6? I know almost nothing about networks, sorry.
IPv6 clients can communicate with IPv6 servers.
IPv4 clients can communicate with IPv4 servers.
In order to mix and match you need some intermediary server that has both IPv4 and IPv6 to translate.
For example my mobile service provider (T-Mobile US) doesn't support IPv4 on their network, however I can still access IPv4 services because they automatically route that traffic through a NAT64 server, which translates the IPv6 from my device into IPv4 heading to the IPv4-only service.
T-Mobile actually takes it a step further than many other IPv6-only service providers. NAT64 alone only solves problems with servers that are IPv4-only, whereas T-Mobile uses 464xlat (which includes NAT64) which also solves problems with apps on the user's device that are IPv4-only.
Sweet, thanks!