• MehBlah@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I tried to roll out ipv6 when I was sysadmin for a small ISP. ARIN gave me a /32 block with no fuss. I started handing them out only to discover most routers at the time couldn’t use them. Not much has changed. No one offers them and I just turned it off at my present job. None of my windows machine have the ipv6 stack enabled.

    • Trainguyrom@reddthat.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      IPv6 genuinely made some really good decisions in its design, but I do question the default “no NAT, no private network prefixes” mentality since that’s not going to work so well for average Janes and Joes

      • r00ty@kbin.life
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        Routers simply need to block incoming unestablished packets (all modern routers allow for this) to replicate NAT security without NAT translation. Then you just punch holes through on IP addresses and ports you want to run services on and be done with it.

        Now, some home routers aren’t doing this by default, but they absolutely should be. That’s just router software designers being bad, not IPv6’s fault, and would get ironed out pretty quick if there was mass adoption and IPv4 became the secondary system.

        To be clear, this is not a reason not to be adopting IPv6.

        • Trainguyrom@reddthat.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          Honestly the more I think about it the more I realize I’m wrong. I was thinking someone could enable a server on their client device without realizing it but the firewall on the router would still need to be modified in that situation, and anything not requiring firewall modifications would be just as much of a security hole on IPv4

          • Encrypt-Keeper@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            4 months ago

            Yeah it’s a common trip up. We’re all so used to the way that things are done in IPv4 that our natural response is to try and apply IPv4 logic to IPv6, but you’re absolutely right.

            Many people think NAT is a security feature but but that’s only a coincidence and it doesn’t do anything a firewall doesn’t already do. And if we take it one step further we can actually see that a firewall and IPv6 is actually more secure than NAT. The only inherent risk of port warding in NAT is that the IP you’re forwarding to is ultimately arbitrary. Think, have a port open to SMB for a publicly accessible file sharing container, then later ditching it and via DCHP your laptop picks up that old IP and now voila you’ve technically exposed your laptop. It’s not quite that simple but that’s the essence of it.

            But with IPv6, IPs are no longer arbitrary. When you allow access in certain ports to a certain machine and that machine goes away, that rule will always only allow access to nowhere.

        • Blackmist@feddit.uk
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          Not the person you were replying too, but I was there when we had modems and raw-dogged the internet.

          The average person clicks “Yes” on everything without reading it, has no idea what a firewall is, and they never update anything unless it does it without asking.

          Having things accessible from outside your network is great if you’re a network nerd and that’s what you want, but most people are going to be in a world of unprotected shit. Especially in a world of pointlessly online devices. I don’t trust any of those fuckers to have their shit in order.

    • Joelk111@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      4 months ago

      As a tech nerd who self hosts stuff, I’m more like “what is IPV6 and why is it causing me issues, I can’t figure this out, I guess I’ll disable it, wow my problems are fixed now.”

      I guess I can see why people don’t like it, as it’s caused me issues, but just because I don’t understand it doesn’t mean it’s dumb. I’d need to understand how it works before I could say anything about it, positive or negative. I guess all I could say is that it’s been way less intuitive to me, I can’t memorize the numbers, and the reason it exists makes sense. Beyond that, I unno.

      I should probably spend the time to learn about it, but I already have a full time job where I work on computers all day, I’d rather focus on my other hobbies while I’m at home.

      • Daemon Silverstein@thelemmy.club
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Back in the days I had an ISP that offered me IPv6 network, it was really easy to self host things over the internet, because IPv6 is unique to all devices, so the server had its own IPv6 global address, which I could access from anywhere with IPv6 connectivity. No more dealing with port forwarding (considering that the ISP didn’t block the forwarding of ports). Just a firewall setting and voila, the service was accessible. It’s that simple.

      • GluWu@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        One restart post-update restarts changed it and helped, but something was still off. Took me like 30 minutes but it looks like my nvidia HDMI audio output got reset to a really low 16 bit sample rate. Got that set back to a decent 24 bit and its closer, but something is still off. I don’t think I had any settings/levels/enchanments.

        • ColeSloth@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          Sounds like windows changed your audio driver. I’d download the most recent audio driver available through nvidia, then uninstall your current audio driver in device manager and manually install nvidias.

  • M0oP0o@mander.xyz
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    “Compromises all devices running … an IPv6 address.”

    Oh so no one is effected. (other then network nerds, and they are not real)

    • froh42@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      IPV6 is already rolled out in parts of the world. My provider has a Dual Stack lite architecture, the home connection is over IPV6, IPV4 is normally being tunneled through a provider grade NAT.

      As I AM a network nerd, I pay for a dedicated IPV4 address every month, so I can reach my stuff from outside from old IPV4 only networks.

        • froh42@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          Because behind the carrier grade NAT I don’t get a routable IPV4 at all, so no inbound connections.

          With the IPV4 I use I do use dyndns now, so I can resolve it from outside.

    • x00z@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Looking at the IP logs of the users on a website of mine shows that many people are already using IPv6 alongside IPv4. Some ISPs even don’t use IPv4 anymore unless you pay extra (Germany/Austria)

    • Scrollone@feddit.it
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Unfortunately (or fortunately, it depends on how you see it), some providers are already on IPv6. My Italian ISP has IPv6 with CGNAT, so all its users are on IPv6 without even knowing what it is.

      • M0oP0o@mander.xyz
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Dang Italian network nerds! That will teach them for believing in a better tech future.

  • Blaster M@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    4 months ago

    To note: It shows even Windows Server 2008 as affected. Since MS is only testing against OSses they support, it is possible this has existed as a problem all the way back since IPv6 was first introduced to Windows XP.

    Also, for all of you “disable IPv6 because I don’t understand it” people… unless you are running Windows 8 or older, just update Windows. IPv4 has been out of addresses for so long that CGNAT is a thing, which means connectivity problems when you’re hosting stuff, and more latency and packet drops from ISP routers getting saturated with NAT tasks. IPv6 is alive on the internet since 2011 and very much used on the internet, does not tie up routers by requiring NAT translation, and therefore just performs better. Plus, if you use your network printer’s or network device’s link-local ipv6 to connect locally, you will never have to deal with static ip address or changing ipv4 lan address pain, as link-local (non-routable on the internet) addresses don’t change unless you force it.

    Also don’t use $35 routers for your internet. If your router does not support ipv6 firewalling, it is long since time to fix that with one that does.

      • Malfeasant@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        I did that years ago, and they said basically “never”. Then a couple years later all of a sudden, there it was.

  • bruhduh@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    Yay, new Xbox jailbreak method, can’t wait for new modded warfare videos about it