Short for Unified Extensible Firmware Interface,UEFI is the low-level and complex chain of firmware responsible for booting up virtually every modern computer.
The flaws reside in functions related to IPv6, the successor to the IPv4 Internet Protocol network address system. They can be exploited in what’s known as the PXE, or Preboot Execution Environment, when it’s configured to use IPv6.
…UEFI(Unified Extensible Firmware Interface) replaces the BIOS(Basic Input Output Software) which was present in the boot ROM(Read Only Memory) of all personal computers …
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
Slaac does everything for you. You get dynamic public addresses that change (you can disable if you please). Nothing to deal with, just open a firewall port if you want to receive traffic
I want static addresses on my LAN, and addresses I can remember and easily recognize in a list. And I don’t want my devices to have unique addresses outside my LAN, especially not static ones.NAT is great.
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. Every device having multiple addresses just complicates things.
A device on your private IPv4 network can send packets directly to 104.21.36.127 via NAT. How will it send packets to 2606:4700:3033::6815:247f? There’s not enough space in the IPv4 header.
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”
and : https://en.m.wikipedia.org/wiki/UEFI
When does a machine ever need IP6?
When it is running in a modern, I.e. IPV6 network?
None of you have given any reason a private address space needs 6
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.
When you want the private network to connect to a public IPv6 network. Most people connect their LANs to the public Internet
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
For private address space you never need 6.
If you want to be able to connect to IPv6 services in the Internet you do.
Ipv6 is the replacement for ipv4. There now exist networks without ipv4
To expand on this, we have functionally ran out of IPv4 addresses. Meaning IPv6 addresses are required.
Not only that, but ipv6 makes networking easier and less complicated. No longer, needing port forwarding or NAT, amongst other improvements
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?
NAT is not security. We aren’t talking about replacing friewalls.
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.
Slaac does everything for you. You get dynamic public addresses that change (you can disable if you please). Nothing to deal with, just open a firewall port if you want to receive traffic
I want static addresses on my LAN, and addresses I can remember and easily recognize in a list. And I don’t want my devices to have unique addresses outside my LAN, especially not static ones. NAT is great.
You can statically number a LAN with fd00::/8 and NAT66 to the internet, if you really want to.
Nothing stops you doing that with ipv6. NAT is complicated and unnecessary.
Only for the internet, not private space
No shit.
But a private Lan will never need it.
There are 4 billion+ possible IP v4 addresses, nearly 600 million in the current private range.
Show me a private network with 600 million devices.
There’s no reason a device that doesn’t have a direct internet connection needs IP6.
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. Every device having multiple addresses just complicates things.
A device on your private IPv4 network can send packets directly to
104.21.36.127via NAT. How will it send packets to2606:4700:3033::6815:247f? There’s not enough space in the IPv4 header.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”
PXE works on ipv4, did gobs of it over the years.
whoosh
Running matter/thread for safer IoT