News for hackers. Stuff that matters.

A comment on Tell HN: IPv6-only still pretty much unusable. Parent comment

Re:Tell HN: IPv6-only still pretty much unusable by theamk on Wednesday December 07, 2022 @04:28PM (#33900534)
Or you extend on network level, and even kernel level, but keep programming API compatible. I don't think people like IPv4 packets that much, it is all the APIs which are giving problem.

I bet if we kept everything about IPv6 the same, but (1) made IPV6_V6ONLY mandatory and default to zero (2) did not use colon in IP address representation (3) recommended firewalls use same config rules for IPv4/IPv6 address.. then IPv6 would have significantly higher adoption right now.

[ Parent | on HN ]
Re:Tell HN: IPv6-only still pretty much unusable by wbl on Wednesday December 07, 2022 @06:15PM (#33901771)
That mistake was already baked in to the sockaddr_t ABI.
[ Parent | on HN ]
Re:Tell HN: IPv6-only still pretty much unusable by p_l on Wednesday December 07, 2022 @07:30PM (#33902456)
BSD Sockets were one giant mistake of not enough abstraction and leaky implementation internals like that.
[ Parent | on HN ]
Re:Tell HN: IPv6-only still pretty much unusable by GoblinSlayer on Thursday December 08, 2022 @11:28AM (#33909764)
On Windows firewall matches ip4 and ip6 with the same rule. The address field there isn't numeric, but text, and can be ip4 address, ip4 network, ip6 address, ip6 network, address range, gateway or "any". Most rules specify "any" for addresses and focus more on ports, application paths and subprotocols like TCP/UDP.
[ Parent | on HN ]