3 ms·
I hope it will support IPv6. The article mentions DHCP and has an example address of 1.2.3.4, but IPv4 seems like a poor choice for a new LAN protocol in 2013.
by oofabz 13y ago
I hope it will support IPv6. The article mentions DHCP and has an example address of 1.2.3.4, but IPv4 seems like a poor choice for a new LAN protocol in 2013. Not everyone has IPv6 internet connectivity but we do all have IPv6 LAN.
Apple has been using IPv6 for local network services for years now, like file sharing and Time Capsule backups, and it works great.
- whalesalad 13y agoWell on an internal network ipv4 is more than enough. With subnets you can put a LOT of hosts on your private network without any problems.
- oofabz 13y agoIPv4 is not just about larger address space. It has better autoconfiguration, better multicast, better MTU, and it has a constant size header to make routing easier. Unlike IPv4, it works well with no centralized server assigning IP addresses - between link-local addresses and multicast, you get everything you need to communicate locally, automatically. It is a good protocol and we should use it because it is good, not just because address space exhaustion forces us to.
- whalesalad 13y agoThanks a lot for the reply. I'm actually really interested in learning more about IPv6 now for all those reasons you mentioned.
- Daniel_Newby 13y agoIPv6 has gigantic variable-length headers. That is inefficient, and too hard to implement in FPGA/silicon for a niche exploratory project.