What #IPv6 also would solve, besides address scarcity, would be those weird feuds where companies that fail in their not policy compliant grab of address space seek out to destroy the RIR system using gaslighting
And I am again in need of an #IPv6 range for NAT66 use cases. It needs to be local routable, but without the special handling of fc00::/7.
In the past I used 200::/16, fe00::/16, all in unassigned space.
Yes, I don’t like NAT66 either.
I just spent a day trying to debug my OpnSense router IPv6 config, after my current ISP started a campaign to invite all of their users to enable it.
In a support call just now, I was advised that the commissioning and deployment at their end has not been completed, so it would not have worked anyway.
Not sure I should shame then openly, but I would have thought that completing the commissioning before encouraging customers is much better than inviting thousands of people to waste their time.
ChatGPT, Create a sonnet about the struggle of #IPv6 adoption in the Internet
Amid the digital realm, a battle waged,
IPv6, a protocol unseen,
Yet in its promise, a future staged,
A struggle vast, where change remains between.
IPv4, the stalwart of the past,
Its address space exhausts, a limit near,
In cyberspace, a crisis unsurpassed,
The march of time, a call we now must hear.
(1/2)
I remember seeing public IPv4 addresses from Xerox and the US DoD assigned to DTAG LTE SIMs internally in Germany (04/2020), probably because they ran out of RFC1918 space. Do you have other such examples? I would like to collect them. (boosts in the IP/ net admin bubble appreciated!)
#ipv4 #telco #networking #network #telekom #sysadmin #ipv6 #cgnat #nat #rfc1918 #internet #dtag #bgp #dfz
I think we’ve reached a point where the question is no longer “What benefit do I gain by building my networks with #IPv6 enabled?” but “What restrictions do we have that require us to omit it?”
IPv6 - so geht's!
IPv6 Praxis-Workshop @ IPB Berlin
It is the end of 2024. #IPv6 should be turned on, it should be the default in most networked software and your (residential) ISP should be giving you a static /48.
#ripe86 #ipv6 #tutorial #ipv6basics #ipv6only
#ipv6transition #dualstack #uptodate #nat64 #464xlat #dslite
#video
https://ripe86.ripe.net/archives/video/993/
#pdf
https://ripe86.ripe.net/presentations/33-RIPE86-IPv6-Tutorial.pdf
Great work by @Oskar456
#ipv6mostly
#ipv6
#ipv6only
#ripe87
#tutorial
#openwrt
https://ripe87.ripe.net/programme/meeting-plan/tutorials/
https://ripe87.ripe.net/wp-content/uploads/presentations/8-IPv6-mostly_on_OpenWRT.pdf
Good news for #IPv6 users in Austria: Apparently, Wien Energie can now deliver state of the art Internet to homes. Handing out a single /128 seems like a curious choice, but you get a /56 through prefix delegation, which should suffice for most homes.
The #Czech state administration has set an end-date for supporting IPv4: June 2032. After that state administration services will only be available over #IPv6. I guess this gives ISPs there eight years to get IPv6 deployment from ~18% of end-users to 100%! https://konecipv4.cz/en/
🌟 Introducing BSD.cafe 🌟
Excited to present the first building block of the BSD Cafe project! When I registered this domain months ago, I envisioned a themed bar where we can casually chat about *BSD systems, Linux, and Open-Source technology among friends, acquaintances, and patrons. But like any bar, discussions can cover a wide range of topics while respecting everyone.
BSD.cafe will be a hub for various tools and services, powered by *BSD.
The first brick is a new Mastodon instance, a gateway to the Fediverse. Registration is open, and the server will be moderated under clear guidelines promoting good behavior and zero tolerance for hate towards anyone. Inclusivity, respect, and constructive dialogue are the key values of this new instance.
The main server is currently hosted in Finland on a small VM, based on #FreeBSD. Services are divided into VNET jails, connected in a LAN via a local bridge. A VPN system is also present and have been able to move individual jails to different, more powerful, machines.
Multimedia data and cache are hosted on another physical server (FreeBSD, within a jail), with Cloudflare in front. The aim is to cache and geodistribute data, reducing network traffic on the main VPS.
Reverse proxy (frontend), mail server, media server, and the instance itself are reachable via #ipv6.
The instance started empty. No unnecessary content was pre-loaded; I want it to grow organically based on users' interests and following. There won't be any preemptive blocks at this stage. Users are encouraged to promptly report anything they find worth flagging.
Join us at https://mastodon.bsd.cafe to build a constructive and inclusive community—a safe and relaxing space for everyone.
Our wiki, located at https://wiki.bsd.cafe, features essential links and articles related to the BSD world. It provides an overview of the tools, services, rules, uptime, and more information about the BSD Cafe Services.
A Matrix server, a Miniflux RSS Reader, the Wiki itself, and the BlendIT Lemmy instance are all part of the BSD Cafe services, with more to come.
#BSD #OpenSource #Fediverse #Community #Tech #Networking #Mastodon #Inclusivity #FreeBSD #NetBSD #OpenBSD #DragonflyBSD #Linux #OSS #SysAdmin #Miniflux #RSS #Matrix