home.social

#ipv6 — Public Fediverse posts

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

  1. @cryptomancer
    Many mastodon instances are lacking outgoing #IPv6, they fail to federate with #IPv6only instances.

    #IPv4 #Mastodon #IPv6 #Snac2 #IPv4

  2. @cryptomancer
    Many mastodon instances are lacking outgoing #IPv6, they fail to federate with #IPv6only instances.

    #IPv4 #Mastodon #IPv6 #Snac2 #IPv4

  3. @cryptomancer
    Many mastodon instances are lacking outgoing #IPv6, they fail to federate with #IPv6only instances.

    #IPv4 #Mastodon #IPv6 #Snac2 #IPv4

  4. @cryptomancer
    Many mastodon instances are lacking outgoing #IPv6, they fail to federate with #IPv6only instances.

    #IPv4 #Mastodon #IPv6 #Snac2 #IPv4

  5. @cryptomancer
    Many mastodon instances are lacking outgoing #IPv6, they fail to federate with #IPv6only instances.

    #IPv4 #Mastodon #IPv6 #Snac2 #IPv4

  6. @lamp.bsky.social
    Roaming?

    Typically the Apple Profile is incorrect.
    #ipv6

  7. @lamp.bsky.social
    Roaming?

    Typically the Apple Profile is incorrect.
    #ipv6

  8. @lamp.bsky.social
    Roaming?

    Typically the Apple Profile is incorrect.
    #ipv6

  9. why does #ipv6 fail to work? this time it's not windows or android or mikrotik, it's ios and t-mobile and sagencomm.

  10. why does #ipv6 fail to work? this time it's not windows or android or mikrotik, it's ios and t-mobile and sagencomm.

  11. why does #ipv6 fail to work? this time it's not windows or android or mikrotik, it's ios and t-mobile and sagencomm.

  12. If I understand #SCTP multihoming correctly, in a multi-WAN scenario, it would likely suck on #LegacyIP because internal hosts usually don't have a NAT44 address routed through each ISP.

    But on #IPv6, multiple addresses is the norm and I think an RA could advertise every ISP's IPv6 prefix, allowing hosts to be aware of their public IPs, thus do sensible SCTP multihoming.

    That sounds awesome! What am I missing, besides application support for SCTP?

  13. If I understand #SCTP multihoming correctly, in a multi-WAN scenario, it would likely suck on #LegacyIP because internal hosts usually don't have a NAT44 address routed through each ISP.

    But on #IPv6, multiple addresses is the norm and I think an RA could advertise every ISP's IPv6 prefix, allowing hosts to be aware of their public IPs, thus do sensible SCTP multihoming.

    That sounds awesome! What am I missing, besides application support for SCTP?

  14. If I understand #SCTP multihoming correctly, in a multi-WAN scenario, it would likely suck on #LegacyIP because internal hosts usually don't have a NAT44 address routed through each ISP.

    But on #IPv6, multiple addresses is the norm and I think an RA could advertise every ISP's IPv6 prefix, allowing hosts to be aware of their public IPs, thus do sensible SCTP multihoming.

    That sounds awesome! What am I missing, besides application support for SCTP?

  15. If I understand #SCTP multihoming correctly, in a multi-WAN scenario, it would likely suck on #LegacyIP because internal hosts usually don't have a NAT44 address routed through each ISP.

    But on #IPv6, multiple addresses is the norm and I think an RA could advertise every ISP's IPv6 prefix, allowing hosts to be aware of their public IPs, thus do sensible SCTP multihoming.

    That sounds awesome! What am I missing, besides application support for SCTP?

  16. If I understand #SCTP multihoming correctly, in a multi-WAN scenario, it would likely suck on #LegacyIP because internal hosts usually don't have a NAT44 address routed through each ISP.

    But on #IPv6, multiple addresses is the norm and I think an RA could advertise every ISP's IPv6 prefix, allowing hosts to be aware of their public IPs, thus do sensible SCTP multihoming.

    That sounds awesome! What am I missing, besides application support for SCTP?

  17. Eine neue #Episode des #Zeroday #Podcast ist #online: 0d133 – IP Leaks

    Link zur Episode: 0x0d.de/2026/05/0d133-ip-leaks/

    Während Sven nichtsahnend die news gelesen hat, schlich sich ein Thema in seinen Fokus. Getrieben von der Frage “Was ist ein IP-Leak?” Begab sich Sven auf

    @[email protected] (Stefan)
    @zeroday (Sven)

    #Datenschutz #DNS #Informationssicherheit #IPLeaks #IPv2 #IPv6 #ITSecurity #ITSicherheit #privacy #Privatsphäre #WebRTC

  18. Eine neue #Episode des #Zeroday #Podcast ist #online: 0d133 – IP Leaks

    Link zur Episode: 0x0d.de/2026/05/0d133-ip-leaks/

    Während Sven nichtsahnend die news gelesen hat, schlich sich ein Thema in seinen Fokus. Getrieben von der Frage “Was ist ein IP-Leak?” Begab sich Sven auf

    @[email protected] (Stefan)
    @zeroday (Sven)

    #Datenschutz #DNS #Informationssicherheit #IPLeaks #IPv2 #IPv6 #ITSecurity #ITSicherheit #privacy #Privatsphäre #WebRTC

  19. Eine neue #Episode des #Zeroday #Podcast ist #online: 0d133 – IP Leaks

    Link zur Episode: 0x0d.de/2026/05/0d133-ip-leaks/

    Während Sven nichtsahnend die news gelesen hat, schlich sich ein Thema in seinen Fokus. Getrieben von der Frage “Was ist ein IP-Leak?” Begab sich Sven auf

    @[email protected] (Stefan)
    @zeroday (Sven)

    #Datenschutz #DNS #Informationssicherheit #IPLeaks #IPv2 #IPv6 #ITSecurity #ITSicherheit #privacy #Privatsphäre #WebRTC

  20. Eine neue #Episode des #Zeroday #Podcast ist #online: 0d133 – IP Leaks

    Link zur Episode: 0x0d.de/2026/05/0d133-ip-leaks/

    Während Sven nichtsahnend die news gelesen hat, schlich sich ein Thema in seinen Fokus. Getrieben von der Frage “Was ist ein IP-Leak?” Begab sich Sven auf

    @[email protected] (Stefan)
    @zeroday (Sven)

    #Datenschutz #DNS #Informationssicherheit #IPLeaks #IPv2 #IPv6 #ITSecurity #ITSicherheit #privacy #Privatsphäre #WebRTC

  21. Eine neue #Episode des #Zeroday #Podcast ist #online: 0d133 – IP Leaks

    Link zur Episode: 0x0d.de/2026/05/0d133-ip-leaks/

    Während Sven nichtsahnend die news gelesen hat, schlich sich ein Thema in seinen Fokus. Getrieben von der Frage “Was ist ein IP-Leak?” Begab sich Sven auf

    @[email protected] (Stefan)
    @zeroday (Sven)

    #Datenschutz #DNS #Informationssicherheit #IPLeaks #IPv2 #IPv6 #ITSecurity #ITSicherheit #privacy #Privatsphäre #WebRTC

  22. 🚀 #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

  23. 🚀 #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

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