3 ms·
That would still require you to have two stacks and two firewall configurations and all of the other things that prevent IPv6 from being turned on. The only th
by jandrese 2y ago
That would still require you to have two stacks and two firewall configurations and all of the other things that prevent IPv6 from being turned on. The only thing you save is by not doing SLAAC and sticking with IPv4-like DHCP you can more easily control things like assigned hostnames, but that's pretty low on the totem pole for blocking issues with IPv6.
- tsimionescu 2y agoSLAAC was just an example, but even here you're downplaying. SLAAC adds a lot of extra complexity: every host now has multiple IP addresses, which was a rarity in IPv4 land, especially for client machines in a LAN; and exactly which IP should be used to identify a host is now highly dependent on details of the network config that are hard to guess (is it using privacy extensions? Will this IP expire daily, or is it more stable?). Plus the dependence on ISPs assigning more than a /64, otherwise SLAAC is broken. And there are also other things - more dependence on ICMP, the concept that your LAN IPs are determined by your ISP (unless you also assign ULAs in addition to all the other IPs), and probably others I'm forgetting.
- Gud 2y agoLinux ifconfig is deprecated. You can pry ifconfig from my cold dead hands.