Comment on New UEFI vulnerabilities send firmware devs industry wide scrambling

• Treczoks@lemmy.world ⁨1⁩ ⁨year⁩ ago

  When it is running in a modern, I.e. IPV6 network?

  source

  • BearOfaTime@lemm.ee ⁨1⁩ ⁨year⁩ ago

    None of you have given any reason a private address space needs 6

    source

    • FrederikNJS@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Because there’s no such thing as private address spaces in IPv6.

      If your ISP is IPv6 only, then you need to enable IPv6 for your local network too, which means that every device on your network gets an IPv6 address.

      You can still have a private IPv4 as well, but if your remove the IPv6 support, then you lose access too the Internet.

      source
    • Supermariofan67@programming.dev ⁨1⁩ ⁨year⁩ ago

      When you want the private network to connect to a public IPv6 network

      source
• ryannathans@aussie.zone ⁨1⁩ ⁨year⁩ ago

  Ipv6 is the replacement for ipv4. There now exist networks without ipv4

  source

  • KairuByte@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

    To expand on this, we have functionally ran out of IPv4 addresses. Meaning IPv6 addresses are required.

    source

    • ryannathans@aussie.zone ⁨1⁩ ⁨year⁩ ago

      Not only that, but ipv6 makes networking easier and less complicated. No longer, needing port forwarding or NAT, amongst other improvements

      source

      • Blackmist@lemmy.world ⁨1⁩ ⁨year⁩ ago

        It’s that necessarily a good thing?

        I remember suddenly needing a firewall on my PC back in the days of the Blaster worm.

        Do we really want all those crappy IoT devices open on all ports to the general internet?

        source

        • -> View More Comments
      • Plopp@lemmy.world ⁨1⁩ ⁨year⁩ ago

        I’d be fucked if I had to deal with IPv6 at home. Give me NAT, port forwarding and a dynamic public address that changes.

        source

        • -> View More Comments
    • BearOfaTime@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Only for the internet, not private space

      source
  • BearOfaTime@lemm.ee ⁨1⁩ ⁨year⁩ ago

    No shit.

    But a private Lan will never need it

    source

    • Nighed@sffa.community ⁨1⁩ ⁨year⁩ ago

      Ideally, using just IP6 would be simpler, as every device gets a global address. Then you don’t need to mess with NAT, port forwarding and all that bullshit.

      source
• Supermariofan67@programming.dev ⁨1⁩ ⁨year⁩ ago

  A lot of the world, especially Africa and south America, was somewhat later in adopting the Internet and has a much smaller supply of IPv4 addresses. People with ISPs there need IPv6 to be directly connectable without CGNAT

  source

  • BearOfaTime@lemm.ee ⁨1⁩ ⁨year⁩ ago

    For private address space you never need 6.

    source
• thanevim@kbin.social ⁨1⁩ ⁨year⁩ ago

  PXE, or network boot. It is basically never used (and rarely enabled, if ever, by default) by the individual, but can be helpful in, for example, a large scale OS deployment. Say IT has to get their corporate image version of Windows 10/11 installed on 30 new laptops. They could write a ton of flash drives, but it'd be easier to just host a PXE boot server and every laptop just listen to them.

  V6 specifically in that instance would just be for the reason of "we need to move away from v4 anyways"

  source

  • BearOfaTime@lemm.ee ⁨1⁩ ⁨year⁩ ago

    PXE works on ipv4, did gobs of it over the years.

    source

    • corsicanguppy@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      whoosh

      source
• BKXcY86CHs2k8Coz@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  Running matter/thread for safer IoT

  source