• raldone01@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      13 days ago

      My wired carrier only gives me a /60 for ipv6 and they can’t do reverse DNS entries for ipv6. :(

      At least I get an ipv6.

  • treadful@lemmy.zip
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    13 days ago

    I gotta suck it up and learn IPv6. My ISP now provides me with a /64. But I feel like I have a lot of knowledge gaps on their features so I’m worried about security. Especially with all the new features like SLAAC.

    What’s the best crash course these days? Go through Cisco materials or something?

  • shortwavesurfer@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    13 days ago

    My ISP gives me my own IPv6, and I have shared IPv4 with CGNAT, but unfortunately, they can’t assign me a static v6, so that I can have servers and stuff. So I just do things like that over Tor. Though things like Tor need work as well, because you’re not able to have a Tor relay on IPv6. You need V4 for that.

    • mschae@discuss.mschae23.de
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      13 days ago

      What makes you say that? As far as I can tell, the only actual downside of it is having to type longer addresses sometimes, but one should really just use the DNS for that. And a bigger address space was needed. Everything else seems better or at least simpler. Autoconfiguration (SLAAC), only one loopback address (which is shorter than any of IPv4’s loopback addresses), subnetting, no need for NAT, proper support for multiple addresses per interface…

      In practice, most problems with IPv6 probably just come from bad support for it in software. That means they should be improved, not that IPv6 was a failure. Also check that you’re not blocking ICMP6 traffic in a firewall or similar (or at least allow the things SLAAC and neighbor discovery need).