Oh, great. #YouTube thinks some large chunks of our #IPv6 ranges are creating unusual traffic.

The odd thing is that we have 2 large ipv6 ranges and at least two /64's ( one from each ) are blocked where other /64's are not.

And #ipv4 seems to be unaffected.

Looks like others are complaining about something similar at downdetector.com as well.

Formation en ligne "Comprendre et déployer le protocole IPv6"

La pénurie d’IPv4 pénalise les nouveaux entrants et augmente les coûts.

🎤 Formation par @bortzmeyer qui vous accompagnera pour organiser la transition de votre réseau vers IPv6 permettant un adressage évolutif et extensible.

🎯 Pour qui ?

Administrateurs système et réseaux, DSI et RSI

📅 La prochaine session aura lieu du 28 au 29 mai

ℹ️ Programme et inscription 🔗 https://www.afnic.fr/produits-services/formations/ipv6/

#Afnic #Formation #IPv4 #IPv6

i am having the wildest time. #IPv4 sort of works but bot quite. #IPv6 is definitely borked. and they dont 't seem to know what is up
@hallunke23 Btw, there are already plenty of #IPv6only websites (see https://www.vypiname.cz/en/ for a list of those I’m aware of). And Czech Republic has a policy in place that demands the state to work on fully deploying #IPv6 (this is centrally coordinated and monitored, annual reports are available to the public) and to *shut down* #IPv4 on 2032-06-06 (this concerns all state services).
@generalx I use bunny so people that are stuck on #IPv4 can access my #IPv6only only content. I’ve moved on having to support legacy protocols and port redirection cludge. #IPv6

OH: Issue ist, dass die xzy-API auf der IPv4 nicht hoch kommt. Auf IPv6 ist sie da, aber es gibt keine IPV6 Adressen auf dem Host.

Mal was neues.

#OH #IPv6 #IPv4

Yess!! Success!

I finally have public IPv4 working on my internet router infrastructure 🎉

~ ❯ ping -c 3 194.28.98.217
PING 194.28.98.217 (194.28.98.217) 56(84) Bytes an Daten.
64 Bytes von 194.28.98.217: icmp_seq=1 ttl=52 Zeit=46.4 ms
64 Bytes von 194.28.98.217: icmp_seq=2 ttl=52 Zeit=43.5 ms
64 Bytes von 194.28.98.217: icmp_seq=3 ttl=52 Zeit=47.3 ms

Now my "hobby ISP" is dual-stack and I have working connectivity in both worlds ..

IPv6: 2a06:9801:1c::/48 -- via BGP (AS201379)

IPv4: 194.28.98.216/29 -- routed to me via Transit-Provider

#internet #routing #ipv4 #ipv6 #dualstack

Yes and No.
#IPv6 rollout is going way to slow. Reason for that is the network effect which is still stronger on legacy #IPv4 than on #IPv6. Still, we have almost reached the 50% mark and at some point in the next few years, we will reach the point where it will become politically feasible for some actors to go #IPv6only. When that happens, the network effect will tip. I'm not sure when exactly that tipping point is going to happen but I think it will happen (1/2)
@ironicbadger @Tubsta
linux/net/ipv4/ipconfig.c at v6.19 · torvalds/linux

Linux kernel source tree. Contribute to torvalds/linux development by creating an account on GitHub.

GitHub