#IPv6 is anti-capitalist.
IPv4 address space is an exploitable scarcity that ISPs do not want to give up. We can’t each have our own IPv4 address, so money determines who gets one (or more.) By design, IPv6 gives every network 2^64 addresses and there are 2^64 of those networks. It is difficult to conceive of a way to use enough of it to ever be constraining. #InfoSec#Sysadminnery… (1/2)
One of my home ISPs enabled #IPv6 services yesterday. I’ve not had IPv6 at home in 6,5 years when my two ISP options discontinued IPv6 support in the same month. Unfortunately, it was my slow non-symmetric backup provider that enabled IPv6 and not my main symmetric-gigabit speeds provider. I’ll probably need to turn off IPv6 on my end to keep routing through the much faster IPv4-only provider. 🤷♂️
Rejoice, network operators. Windows 11 will be joining the rest of the world soon in supporting CLAT, #NAT64, and #DNS64 natively. (Currently, CLAT only works on cellular connections.)
Supporting two IP versions has been a pain we’ve had to live with for over a decade, but this will allow network operators to forcibly disable clients’ IPv4 stacks via DHCP/RA, finish #IPv6 switchovers, and run true #IPv6mostly or #IPv6only networks.
We’re one big step closer to killing “legacy IP” for good.
regarding roaming: IPv4 only suggested 😕
Is anybody here to answer the question, if IPv6 during roaming works, if the setting is changed to IPv6 or IPv4/IPv6 ?
Question regarding #Multicast, especially with #IPv6: Is there any concept of signaling the availability of multicast route(r)s to hosts / potential listeners?
On #Linux I see it as a usability issue/bug that I have to manually type "ip -6 route add ff1e::/16 dev wlp1s0 table local". Otherwise, even for routeable mulicast addresses, listeners will be installed on the first non-localhost interface by default. Which for me is br0, not wlp1s0.
For testing purpose I set up an #IPv6only network with radvd and dhcp6d pointing to a resolving DNS server which itself also only has #IPv6 connectivity. After browsing the web for a short while, I found many websites which I remembered supporting IPv6 failing. Their web servers support IPv6 but their nameservers don't. Some prominent examples are:
Frage an mastodon server Betreiber. Ich habe das Problem, dass unsere Instanz nicht via ipv6 erreichbar ist. Der AAAA Record ist richtig gesetzt und die Firewall korrekt konfiguriert. Ebenso lauscht nginx auf alle ipv6 Adressen. An was kann das noch liegen? OS ist debian 12. #mastodon#ipv6#debian#server#frage#linux@Patrick@Johann150 Danke für den Hinweis
I would like to reply to these "We have IPv4 addresses" spam mails (received via the address in RIPE NCC) with "Lol, Who uses IPv4 anymore? I'm all IPv6"
Købt og solgt som internetkunde i Danmark for tiden. Mit Kviknet overgår til EWII - wiiiiiiiiii eller noget.
Men jeg spurgte dem om #IPv6 og de har svaret: "Vi tilbyder IPv6 via DHCPv6 til alle nyere oprettede abonnementer, oprettet efter medio april 2023. Alle nyere EWII-leverede routere er automatisk sat op til at køre med IPv6. Du kan bruge IPv6 på eget udstyr, men vi kan ikke garantere det vil fungere. "
Some days ago I found an advertisement of #Finemedia ISP in my postbox (in #Wrocław, #Poland). As usual, I sent an email with a question about #IPv6 support (I use Orange, but I'm interesting to have alternative).
Surprisingly, the answered was they can provide an IPv6 /56 network per router.
But I don't see any documentation about it. I see they own 2a02:21a0::/29, but that doesn't mean they use it.
Maybe the Fediverse knows something about Finemedia's IPv6 support for end users?
#IPv6 chez #EDF : Pierre Violet nous explique la stratégie de migration IPv4 ⇒ IPv6 d'#EDF.
La migration IPv6 du SI est complexe et est réalisée brique par brique, sans coupure.
Savez-vous que tous les compteurs Linky sont connectés en IPv6 only ? https://www.youtube.com/watch?v=UBH1ZtQdx0g
"Facebook transitioned to using 100% IPv6 addresses in all of its data centers in 2017, and is working on rolling out IPv6 to the rest of the infrastructure."
Hatte von euch schon mal jemand das Problem, dass beim Mesh der Fritz!Box hinter den Repeatern kein IPv6 funktioniert? An der Fritz!Box selbst geht es ohne Probleme und ich bin scheins gerade zu doof zum googeln.
Die Repeater laufen bei mir übrigens alle als AP, sind also per Cat7 oder Coax an der Fritz!Box, nicht per WLAN. Und sie zeigen in ihrer Oberfläche auch eine IPv6 an und sind per IPv6 pingbar.
Today I've spent ages trying to get to terms with servers that have IPv6 DNS but aren't actually listening on IPv6 and some client libraries that have recently updated and will now (quite rightly, actually) refuse to fallback to IPv4. #ipv6
GitHub Actions is still only use IPv4 for netowork connections and it will fail to connect to IPv6 only networks like Supabase. Here’s a workaround to use IPv6.
@jucktion I've seen this workaround before. It's amazing that #GitHub would rather pay for 500 MB of bandwidth every time I want to do something rather than implement #IPv6.
Fortunately, I hear they're working on it. They recently broke part of the site while testing it.
Add IPv6 compatibility to GitHub Actions with two lines (www.jucktion.com)
GitHub Actions is still only use IPv4 for netowork connections and it will fail to connect to IPv6 only networks like Supabase. Here’s a workaround to use IPv6.