Sorry, you are not “swimming in addresses” There are no CLASS routing addresses any more, that is an old obscure term not used any more Year 1985 is calling to get that term back You got CLASS LESS routing in “modern” IPv4-networks since before 1990You do NOT have a public /16 IPv4 address, you probably have a private one that isn’t routable on Internet Which probably are these private addresses ranges 10000/8 or 19216800/16 The other private address range are not /16 (which is as close to a class B network we now can get)With IPv4, you have to use private addresses, and in best case, you got ONE public IPv4 address on your external interface on your home router with NAT In worst case you will have a CGNAT, and you are really locked down, with slower transfer speeds then you should have, and higher latency then you should have ALL because of then hell of NATA local network (LAN) in IPv6 do have /64 netmask for PUBLIC IPv6 addresses (which basically meant the other 64 of the IPv6 address are nodes, so you have 2^64 IPv6 addresses in your LANThere are only 2^32 total address space for IPv4, not counting that localnet (127000/8) is not usable, nor the private addresses 10000/8 and 19216800/16 and 1006400/10 for CGNAT and a load of other addresses are not usable in IPv4So even if you uses 19216800/16 for your nets with IPv4, you don’t “swimming in addresses” And your ISP should give you /56 networks to route, which is 256 of those /64 public IPv6-networks you get by IPv6 THAT is swimming in addressesAnd why do you need 256 LAN with public addresses? Because it make fire wall much easier and not as prone to errors like IPv6You give a IPv6 LAN to your media machines You give one or two IPv6 LAN to your IoT You give your media and game machines one IPv6 LAN You give your personal phone and gadgets one IPv6 LAN, as with rest of the family And you put one IPv6 LAN for guests to useNow you make firewall rules based on net work and not devices, that share the same LAN Much easier to make safe rules without needing to know every deviceAnd no, you use device names as God meant it to be used, not numerical address
urany
Sorry, you are not “swimming in addresses” There are no CLASS routing addresses any more, that is an old obscure term not used any more Year 1985 is calling to get that term back You got CLASS LESS routing in “modern” IPv4-networks since before 1990You do NOT have a public /16 IPv4 address, you probably have a private one that isn’t routable on Internet Which probably are these private addresses ranges 10000/8 or 19216800/16 The other private address range are not /16 (which is as close to a class B network we now can get)With IPv4, you have to use private addresses, and in best case, you got ONE public IPv4 address on your external interface on your home router with NAT In worst case you will have a CGNAT, and you are really locked down, with slower transfer speeds then you should have, and higher latency then you should have ALL because of then hell of NATA local network (LAN) in IPv6 do have /64 netmask for PUBLIC IPv6 addresses (which basically meant the other 64 of the IPv6 address are nodes, so you have 2^64 IPv6 addresses in your LANThere are only 2^32 total address space for IPv4, not counting that localnet (127000/8) is not usable, nor the private addresses 10000/8 and 19216800/16 and 1006400/10 for CGNAT and a load of other addresses are not usable in IPv4So even if you uses 19216800/16 for your nets with IPv4, you don’t “swimming in addresses” And your ISP should give you /56 networks to route, which is 256 of those /64 public IPv6-networks you get by IPv6 THAT is swimming in addressesAnd why do you need 256 LAN with public addresses? Because it make fire wall much easier and not as prone to errors like IPv6You give a IPv6 LAN to your media machines You give one or two IPv6 LAN to your IoT You give your media and game machines one IPv6 LAN You give your personal phone and gadgets one IPv6 LAN, as with rest of the family And you put one IPv6 LAN for guests to useNow you make firewall rules based on net work and not devices, that share the same LAN Much easier to make safe rules without needing to know every deviceAnd no, you use device names as God meant it to be used, not numerical address