#ipv4 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ipv4, aggregated by home.social.
-
Interessant das mein Post gar nicht ankam:
https://ipv6.camp/@goetz/116639477303284429 -
Interessant das mein Post gar nicht ankam:
https://ipv6.camp/@goetz/116639477303284429 -
Interessant das mein Post gar nicht ankam:
https://ipv6.camp/@goetz/116639477303284429 -
Interessant das mein Post gar nicht ankam:
https://ipv6.camp/@goetz/116639477303284429 -
🚀 #Mumble [FR]BlablaLinux est maintenant en #IPv6 !
Accédez à votre serveur vocal préféré en #IPv4 ou en IPv6 natif.
🔗 Serveur : mumble.blablalinux.be
🌐 IPv6 : 2a02:a03f:b985:a100:be24:11ff:fe8b:9a6f
📢 Port : 64738
#SelfHosted #BlablaLinux #Proxmox -
🚀 #Mumble [FR]BlablaLinux est maintenant en #IPv6 !
Accédez à votre serveur vocal préféré en #IPv4 ou en IPv6 natif.
🔗 Serveur : mumble.blablalinux.be
🌐 IPv6 : 2a02:a03f:b985:a100:be24:11ff:fe8b:9a6f
📢 Port : 64738
#SelfHosted #BlablaLinux #Proxmox -
🚀 #Mumble [FR]BlablaLinux est maintenant en #IPv6 !
Accédez à votre serveur vocal préféré en #IPv4 ou en IPv6 natif.
🔗 Serveur : mumble.blablalinux.be
🌐 IPv6 : 2a02:a03f:b985:a100:be24:11ff:fe8b:9a6f
📢 Port : 64738
#SelfHosted #BlablaLinux #Proxmox -
🚀 #Mumble [FR]BlablaLinux est maintenant en #IPv6 !
Accédez à votre serveur vocal préféré en #IPv4 ou en IPv6 natif.
🔗 Serveur : mumble.blablalinux.be
🌐 IPv6 : 2a02:a03f:b985:a100:be24:11ff:fe8b:9a6f
📢 Port : 64738
#SelfHosted #BlablaLinux #Proxmox -
It always amuses me to see #residential #proxy providers with service in certain regions. As an Internet infrastructure researcher, you folks have a hard time convincing me that you actually managed to leverage #IPv4 addresses linked to hosts residing in #NorthKorea.
-
Eliminated the IPv4 NAT for my blog today and gave the Caddy jail it's own dedicated IPv4 address from my /28 subnet.
Makes the firewall configuration a lot simpler and I can drop all that rdr/nat stuff.. Modern IPv6 of course, always was a routed end-to-end connection.
It's time that we finally leave that legacy IP crap behind at some point .. le sigh.
-
Eliminated the IPv4 NAT for my blog today and gave the Caddy jail it's own dedicated IPv4 address from my /28 subnet.
Makes the firewall configuration a lot simpler and I can drop all that rdr/nat stuff.. Modern IPv6 of course, always was a routed end-to-end connection.
It's time that we finally leave that legacy IP crap behind at some point .. le sigh.
-
Eliminated the IPv4 NAT for my blog today and gave the Caddy jail it's own dedicated IPv4 address from my /28 subnet.
Makes the firewall configuration a lot simpler and I can drop all that rdr/nat stuff.. Modern IPv6 of course, always was a routed end-to-end connection.
It's time that we finally leave that legacy IP crap behind at some point .. le sigh.
-
Eliminated the IPv4 NAT for my blog today and gave the Caddy jail it's own dedicated IPv4 address from my /28 subnet.
Makes the firewall configuration a lot simpler and I can drop all that rdr/nat stuff.. Modern IPv6 of course, always was a routed end-to-end connection.
It's time that we finally leave that legacy IP crap behind at some point .. le sigh.
-
Eliminated the IPv4 NAT for my blog today and gave the Caddy jail it's own dedicated IPv4 address from my /28 subnet.
Makes the firewall configuration a lot simpler and I can drop all that rdr/nat stuff.. Modern IPv6 of course, always was a routed end-to-end connection.
It's time that we finally leave that legacy IP crap behind at some point .. le sigh.
-
El lado del mal - La propuesta del Internet Protocol Version 8 (IPv8) para tener compatibilidad con IPv4 e ignorar IPv6 https://www.elladodelmal.com/2026/05/la-propuesta-del-internet-protocol.html #IPv8 #IPv4 #IPv6 #Redes #Internet #Networking
-
El lado del mal - La propuesta del Internet Protocol Version 8 (IPv8) para tener compatibilidad con IPv4 e ignorar IPv6 https://www.elladodelmal.com/2026/05/la-propuesta-del-internet-protocol.html #IPv8 #IPv4 #IPv6 #Redes #Internet #Networking
-
El lado del mal - La propuesta del Internet Protocol Version 8 (IPv8) para tener compatibilidad con IPv4 e ignorar IPv6 https://www.elladodelmal.com/2026/05/la-propuesta-del-internet-protocol.html #IPv8 #IPv4 #IPv6 #Redes #Internet #Networking
-
El lado del mal - La propuesta del Internet Protocol Version 8 (IPv8) para tener compatibilidad con IPv4 e ignorar IPv6 https://www.elladodelmal.com/2026/05/la-propuesta-del-internet-protocol.html #IPv8 #IPv4 #IPv6 #Redes #Internet #Networking
-
El lado del mal - La propuesta del Internet Protocol Version 8 (IPv8) para tener compatibilidad con IPv4 e ignorar IPv6 https://www.elladodelmal.com/2026/05/la-propuesta-del-internet-protocol.html #IPv8 #IPv4 #IPv6 #Redes #Internet #Networking
-
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 : https://wiki.blablalinux.be/fr/pourquoi-ipv6-est-plus-propre-que-ipv4
Bonne lecture à tous !
-
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.
-
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.
-
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.
-
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.
-
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.
-
Danke für deine Rückmeldung/Test.
#Internet - #IPv6 aktuelles Protokoll
#LegacyNet - #IPv4 veraltetes ProtokollDie 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
-
https://www.europesays.com/afrika/5767/ Afrinic: Regierung von Mauritius schreitet ein #Afrinic #ICANN #Internet #IPv4 #Mauritius #Registry #Wirtschaft
-
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?
-
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?
-
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?
-
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?
-
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?
-
IPV8
When someone says;
"Centralise Everything it is cheaper and easier and more convenient"
Walk away.
Go do something useful with your time.https://lowendbox.com/blog/vibe-drafting-ietf-proposals-is-now-a-thing-the-ipv8-proposal/
https://www.ip.network/blog/what-is-ipv8-protocol
[ 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 :)
-
IPv6 未流行先玩完 IPv8 草案公布 1,844.67 億億位址兼容舊有設備
協助研發網際網路標準的「網際網路工程任務組」IETF 早前公布第 8 版互聯網協定（IPv8）核心協定草案，採 […]
#生活科技 #IETF #IPv4 #IPv6
https://unwire.hk/2026/04/17/ietf-ipv8-draft-ipv4-compatible/life-tech/?utm_source=rss&utm_medium=rss&utm_campaign=ietf-ipv8-draft-ipv4-compatible -
IPv6 未流行先玩完 IPv8 草案公布 1,844.67 億億位址兼容舊有設備
協助研發網際網路標準的「網際網路工程任務組」IETF 早前公布第 8 版互聯網協定（IPv8）核心協定草案，採 […]
#生活科技 #IETF #IPv4 #IPv6
https://unwire.hk/2026/04/17/ietf-ipv8-draft-ipv4-compatible/life-tech/?utm_source=rss&utm_medium=rss&utm_campaign=ietf-ipv8-draft-ipv4-compatible -
IPv6 未流行先玩完 IPv8 草案公布 1,844.67 億億位址兼容舊有設備
協助研發網際網路標準的「網際網路工程任務組」IETF 早前公布第 8 版互聯網協定（IPv8）核心協定草案，採 […]
#生活科技 #IETF #IPv4 #IPv6
https://unwire.hk/2026/04/17/ietf-ipv8-draft-ipv4-compatible/life-tech/?utm_source=rss&utm_medium=rss&utm_campaign=ietf-ipv8-draft-ipv4-compatible -
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:
https://gitlab.com/EinPhysiker/fritzbox-port-forwarderVielleicht findet das ja jemand als Inspiration nützlich.
-
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:
https://gitlab.com/EinPhysiker/fritzbox-port-forwarderVielleicht findet das ja jemand als Inspiration nützlich.
