>>> create-interface is the thing that sets up the phyint/ill, right? >> >> right, and sets up the autoconfigured link-local on it. > > I thought you wanted interface management be separate from address > management, and if that is the goal it probably doesn't make sense to > even do link-locals as part of the interface management. Requires some > careful though at least.
yes, and also some kernel rewhacking, because an "ifconfig link0 inet6 plumb" today will set up the link-local. That behavior makes sense if you consider that an ipv6 interface *must* have at least one link-local address, and the current assumption in the kernel is that the default link-local address is the one obtained by autoconfig. > I don't have a problem with a libipadm create-interface to get those > benefits, but perhaps ipadm can do it implicitly? Why should the admin > doing things manually have to do N steps when the system can figure it > out that > ipadm create-address 1.2.3.4/24 bge0 > means that the user wants bge0 to exist? that would work, but the question remains: what does the function libipadm`ipadm_create_interface() do for the link-local. One choice is that we can make the default behavior to be that the link-local is the autoconfigured one, unless a static link-local is provided as the argument to ipadm_create_interface(). --Sowmini _______________________________________________ networking-discuss mailing list [email protected]
