On 06/18/2015 10:19 AM, Light, John J wrote: > Unfortunately, while an interface can have only one IPv4 address (and > therefore socket), an interface can have an indefinite number of IPv6 > addresses. Creating sockets for each of an indefinite number of interface > addresses is problematical in itself, but the real issue is that the current > approach requires each send message to be sent on the "right" socket. The > current code bothers to find the "right" IPv4 socket (a complicated process > involving comparison of addresses under net masks) before it uses it. That > process is burdensome as it stands, but it would become ridiculous if it were > applied to the IPv6 addresses as well. >
Actually, a single interface can have more than one IPv4 address. That's a special case that was not addressed in the previous networking abstraction IIRC. I'm trying to remember details from when I looked into this a few months back. One key is that ip aliasing is the outdated way to achieve it, so we are looking at multiple ways to get multiple IPs. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com
