home.social

#ipv4 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ipv4, aggregated by home.social.

  1. Salut les libristes ! Vous entendez parler d' #IPv6 sans trop savoir ce que ça change concrètement ?

    J'ai publié une page volontairement très simple ! Ici, pas de lignes de commandes complexes ou de technique pure. C’est une explication claire et accessible, même pour les non-initiés, pour comprendre pourquoi l’IPv6 est plus "propre" que notre vieux #IPv4.

    Bref, de la vulgarisation efficace pour comprendre votre réseau !

    👉 C'est par ici : wiki.blablalinux.be/fr/pourquo

    Bonne lecture à tous !

  2. If your #vps price should go up by +2$/month because of #ipv4, would you still buy it?

  3. At home, on most common network which are statefull #dhcp,

    You usually get an #ipv4 based on your hardware MAC address, this ensures constancy across device reboot, dual boot (and distro hoping 🙈)

    But #ipv6 do not care about the hardware, it will look for a DUID (small string) at /etc/dhcp/duid.

    You can persist this file into your dots for your ipv6 address to survive across OS changes.

    #linux #archlinux

  4. I've reached the point where I no longer use #ipv4 as the default network protocol in #homelab.

    I immediately think in #ipv6 instead!
    And I must admit I prefer the latest! 😀

  5. @pdl @kuketzblog

    Danke für deine Rückmeldung/Test.

    #Internet - #IPv6 aktuelles Protokoll
    #LegacyNet - #IPv4 veraltetes Protokoll

    Die Quote der Internetanschlüsse in Deutschland ist bei >75% die das Internet erreichen. Platz 2 weltweit bei allen westlichen Messungen.

    Deutsche ISP bieten den Zugang zum LegacyNet nur noch als IPv4-as-a-Service an. -> schlechtere/langsamere Erreichbarkeit

    Jeder Dienst ohne IPv6 Support ist nicht im Internet erreichbar. IMHO

  6. Something to consider about all of the efforts to sustain #IPv4 so far beyond its original shelf life. #NAT and #IPv6 were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.

    This brings us to #platforms. It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.

    Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?

    #SaturdayMorningThoughts

  7. Something to consider about all of the efforts to sustain #IPv4 so far beyond its original shelf life. #NAT and #IPv6 were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.

    This brings us to #platforms. It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.

    Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?

    #SaturdayMorningThoughts

  8. Something to consider about all of the efforts to sustain so far beyond its original shelf life. and were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.

    This brings us to . It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.

    Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?

  9. Something to consider about all of the efforts to sustain #IPv4 so far beyond its original shelf life. #NAT and #IPv6 were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.

    This brings us to #platforms. It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.

    Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?

    #SaturdayMorningThoughts

  10. Something to consider about all of the efforts to sustain #IPv4 so far beyond its original shelf life. #NAT and #IPv6 were thought out at roughly the same time. NAT was a tactical move to stave off IPv4 exhaustion (at the cost of limiting the peer-to-peer nature of the Internet) and IPv6 was the strategic answer for scalable growth. The obsession human beings have to find any excuse to avoid change was highly underestimated. IPv6 took 22 years to become an Internet Standard and NAT became so entrenched that peer-to-peer networking became mostly unnecessary as long as we could continue to laugh at cat memes on our favourite platforms.

    This brings us to #platforms. It’s getting harder to host anything ourselves anymore without paying a (usually foreign) IaaS/SaaS platform to do it for us. We now live in an age where data sovereignty and privacy are at the forefront of our thinking and maybe, just maybe, we want other options.

    Is our obsession with IPv4 tying us unhealthily to platforms and sacrificing our freedoms?

    #SaturdayMorningThoughts

  11. IPV8

    When someone says;

    "Centralise Everything it is cheaper and easier and more convenient"

    Walk away.
    Go do something useful with your time.

    lowendbox.com/blog/vibe-drafti

    ip.network/blog/what-is-ipv8-p

    [ edit for a mistake with my pasting of links.]

    IF the big corps/tech bros back this protocol ... then you really know.

    Networks do distribution.
    The above links cover this way better and more cogently than I ever will.
    (or could)

    My knowledge base here is too many layers down :)

    #Protocol #Networking #IPV8 #IPV4
    #IPV6 ?

  12. Wie ich letzte Woche geschrieben habe, wurde mir ja meine öffentliche #IPv4 genommen, weil mein Provider jetzt #CGNAT macht. Jetzt wollte ich aber weiterhin aus #IPv4only Netzen zumindest mein Wireshark VPN starten können.

    Meine Lösung hat angefangen mit einer einfachen #socat Zeile auf einem VPS. Da ist dann in den letzten Tagen immer mehr dazu gekommen: automatischer Start, automatischer Restart, DynDNS Handling, konfigurierbare Weiterleitungen. Das ganze läuft jetzt auf einem separaten 1€ VPS.

    Solche Lösungen sind nicht neu, aber ich habe das alles mal zusammengefasst und auf GitLab gepackt:
    gitlab.com/EinPhysiker/fritzbo

    Vielleicht findet das ja jemand als Inspiration nützlich.

  13. IPv8 выглядит как мечта. Поэтому почти наверняка не взлетит

    В IETF появился draft, который обещает интернет без dual-stack, без CGNAT и без мучительного перехода. Спасение для всех, кто двадцать лет тащит IPv6 в гору, не станет будущим сети. draft-thain-ipv8-00 , опубликованный 14 апреля 2026 года на бумаге выглядит слишком хорошо: IPv4 становится подмножеством IPv8, dual-stack будто бы больше не нужен, каждому владельцу ASN достаётся по 2^32 адресов хостов, а сеть получает единую управляемую платформу вместо нынешнего зоопарка из разрозненных сервисов. История с IPv8 интересна не как новость про новый IP-протокол. Она очень громко показывает, насколько индустрия устала от бесконечного, вязкого и дорогого перехода на IPv6. Читать, почему IPv8 это сказка

    habr.com/ru/articles/1024322/

    #ipv6 #ipv4 #ipv8

  14. @q iMsys or mMe

    iMsys (the smart meter gateway with the LTE-M modem) is unfortunately #IPv4 only and Mobile Network Operators have to have NAT64 / PLAT until eternity.

    And users of the HAN as well.

    :-(

  15. Öffentlich oder Privat? Verstehe die IP-Architektur, wie #NAT funktioniert und warum IPv6 die Zukunft ist. Mit praktischen Linux-Beispielen zur Netzwerkanalyse, Tools wie ip und #nmap sowie Tipps zur Fehlerbehebung.

    admindocs.de/de/netzwerk/oeffe

    #netzwerk #ipadressen #ipv4 #ipv6 #sicherheit #firewall #troubleshooting #sysadmin

  16. My current public #IPv4 address ends 225.226.227. So that makes it easy to remember for the extremely unlikely event of me needing to tell it to someone.

  17. You want the #dhcp to yield the same #ipv4 everytime -> ensure your MAC address is fixed.

    For the #dhcp to yield the same #ipv6-> ensure /var/lib/dhcpcd/duid
    contains a fixed user-defined duid-uuid.

  18. Ah, the utopian dream of an IPv6-only household 🌐, where unicorns roam free and every device magically supports the latest protocol. But alas, reality crashes the party 🎉, with antiquated #IPv4 clinging on harder than Windows XP in a corporate office. Remember, if it doesn’t work, just throw more tech acronyms at it! 🙄
    varunpriolkar.com/2026/03/buil #IPv6 #Utopia #Struggles #TechAcronyms #NetworkChallenges #HackerNews #ngated

  19. Ah, the utopian dream of an IPv6-only household 🌐, where unicorns roam free and every device magically supports the latest protocol. But alas, reality crashes the party 🎉, with antiquated #IPv4 clinging on harder than Windows XP in a corporate office. Remember, if it doesn’t work, just throw more tech acronyms at it! 🙄
    varunpriolkar.com/2026/03/buil #IPv6 #Utopia #Struggles #TechAcronyms #NetworkChallenges #HackerNews #ngated

  20. Ah, the utopian dream of an IPv6-only household 🌐, where unicorns roam free and every device magically supports the latest protocol. But alas, reality crashes the party 🎉, with antiquated #IPv4 clinging on harder than Windows XP in a corporate office. Remember, if it doesn’t work, just throw more tech acronyms at it! 🙄
    varunpriolkar.com/2026/03/buil #IPv6 #Utopia #Struggles #TechAcronyms #NetworkChallenges #HackerNews #ngated

  21. Ah, the utopian dream of an IPv6-only household 🌐, where unicorns roam free and every device magically supports the latest protocol. But alas, reality crashes the party 🎉, with antiquated #IPv4 clinging on harder than Windows XP in a corporate office. Remember, if it doesn’t work, just throw more tech acronyms at it! 🙄
    varunpriolkar.com/2026/03/buil #IPv6 #Utopia #Struggles #TechAcronyms #NetworkChallenges #HackerNews #ngated

  22. Ah, the utopian dream of an IPv6-only household 🌐, where unicorns roam free and every device magically supports the latest protocol. But alas, reality crashes the party 🎉, with antiquated #IPv4 clinging on harder than Windows XP in a corporate office. Remember, if it doesn’t work, just throw more tech acronyms at it! 🙄
    varunpriolkar.com/2026/03/buil #IPv6 #Utopia #Struggles #TechAcronyms #NetworkChallenges #HackerNews #ngated

  23. @hallunke23 Btw, there are already plenty of #IPv6only websites (see 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).

  24. 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

  25. New Project Idea:

    LLM based Scam-Baiting Stack for unsolicited IP Broker Spam Mails.

    Who's in?

    #IPv4 #Spammers

  26. Just for checking the possibilities I’ve migrated my #LDAP server from 389ds to OpenLDAP on #NetBSD 10.1 and put in on the #aws. It’s look like that t4g.nano is able to handle my load. Without #IPv4 costs is quite small. Of course migration LDAP engine was done with pain, unfortunately but still possible.

  27. OK, this may seem like a very simple question, but I've found it extremely hard to get a definite answer:

    Is it possible, in this year of our FSM 2026, to maintain a direct TCP or UDP connection between a home network and a mobile device which are BOTH behind CGNAT?

    I assume that the connection setup at least will require some external 3rd-party bounce host with a public IP, but once that's out of the way, can we still have a direct P2P connection?

    #networking #ipv4 #tcp #udp

  28. #AIS #Fibre #Thailand ist wohl #IPv6 only und genau diesmal muss ich nen Device erreichen, dass ich direkt nur per #IPv4 erreichen kann. Ich muss unbedingt eine Route in Tailscale zu dem Netz hinzufügen.
  29. Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.

    Tonight, my IPv6 connection to the internet went away.

    as13030.net/status/?ticket=423

    Is «IPv4 only» the new reliability? 🤔
    Did I miss something? 😉

    #ipv6 #ipv4 #maintenance #init7

  30. Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.

    Tonight, my IPv6 connection to the internet went away.

    as13030.net/status/?ticket=423

    Is «IPv4 only» the new reliability? 🤔
    Did I miss something? 😉

    #ipv6 #ipv4 #maintenance #init7

  31. Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.

    Tonight, my IPv6 connection to the internet went away.

    as13030.net/status/?ticket=423

    Is «IPv4 only» the new reliability? 🤔
    Did I miss something? 😉

    #ipv6 #ipv4 #maintenance #init7

  32. Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.

    Tonight, my IPv6 connection to the internet went away.

    as13030.net/status/?ticket=423

    Is «IPv4 only» the new reliability? 🤔
    Did I miss something? 😉

    #ipv6 #ipv4 #maintenance #init7

  33. @eXo_X5
    Translation
    Stories from the life of an admin:
    Yesterday I was sitting in a pleasantly sparsely occupied IC train of the from Berlin to Magdeburg.
    To pass the time, I wanted to tinker with a few devices via the train’s .
    Since they don’t have their own addresses, they can only be reached over using several hops. There is no in the Bahn wifi.
    No problem, I thought – that’s why I have my with IPv6.
    And that’s where our story begins:
    1/6

  34. Just had a discussion on routable #IPv4 address space. This lead me to check #Bogon IP address space. I briefly fetched a public bogon list of a large provider, parsed the CIDR blocks and calculated the number of IPv4 addresses. Dividing this by 0.0.0.0/0 eventually lead to the discovery that 13.89% of the IPv4 address space is non-routable. Way more than I had anticipated.

    Your daily dose of #netops knowledge... :)

  35. @marlin
    Hier ein paar Infos über die zusätzlichen Angriffsvektoren bei #IPv6. Bei richtiger Konfiguration ist IPv6 natürlich nicht unsicherer als #IPv4.

    #netsec #ITSecurity #networking #netzwerke #Rechnernetze #Shodan #IP #Internet
    @bsi

  36. Темная история IPv6: почему мы 30 лет «переходим», но так и не перешли

    IPv6 больше четверти века обещает избавить интернет от тесноты IPv4-адресов. Его называли будущим сети, устраивали тестовые «дни IPv6», грозили скорым цифровым апокалипсисом IPv4… Но на дворе уже конец 2025 года, а IPv4 всё ещё живее всех живых. Почему за 30 лет мы так и не перешли на IPv6? Попробую разобраться в этой тёмной (и местами ироничной) истории. Читать

    habr.com/ru/companies/ruvds/ar

    #IPv6 #протокол #сеть #сетевые_технологии #интернет #IPv4 #RFC #хостинг #провайдеры #ruvds_статьи

  37. Hmmm, #NANOG discusses #IPv4 pricing falling below $20. There is also a claim that North-American ISPs sell much of their IPv4 space. Why is that happening? Is it, because #IPv6 is now the preferred method?

    #routing #bgp #netops

  38. I have contacted Contabo: "I will be ordering multiple VPS in Singapore. Ensure your infrastructure, including IPv6, is functioning properly, as no refunds are offered. Customer support is slow and misaligned with my schedule. Confirm IPv4, IPv6, and overall infrastructure are fully operational."

    #Contabo #VPS #CustomerService #IT #Networking #IPv6 #IPv4 #Infrastructure #Reliability #TechDemand #SelfHosting #SingaporeRegion #TechIssues #ContaboSupport #CircadianCycle