People who advocate for IPv6 are always like 'ahhhh just plug it in and its ready to go!!!' There's …
People who advocate for IPv6 are always like 'ahhhh just plug it in and its ready to go!!!' There's even twitter accounts that shame people for how they approach IPv6. But after doing a crap load of network programming I can tell you its really not simple at all. - IPv6 has many different address types. - Depending on the type you want to bind to it needs to be handled different. - Some types need an interface ID appended to them. - This is conditional on the type of the OS. - Windows has no easy way to get the ID programmatically. - Some address types need additional bind info like the 'scope id.' - Whether you can reach a specific addr type in a con depend on the addr you bind to. - IPv6 was designed to have plenty of addresses so that NAT isn't needed. Guess what: IPv6 can still do NAT like NAT6. In which case you won't have any nice global scope addresses to bind to. Writing good network code depends on being able to list the interfaces on a machine and the addresses that they have. …
Original discussionDHCPv6-PD – First Steps83 source comments · at import