On (04/22/09 15:03), Erik Nordmark wrote: > > But it still leaves out the -i link0 for a delete-dhcp. Given that we > can't leave out -i link0 for a delete-address it would make sense to > have it consistently require -i. Thus the name space for <label> becomes > local to the interface name.
Ok, we can do that. >>> What is the name space for that name? By that I mean whether or not I can do >>> ipadm create-dhcp4 -i link0 default >>> ipadm create-dhcp6 -i link0 default >>> or whether that tells me the object called "default" already exists. >> >> If you specified it as above, then "default" would be considered the label. >> A label must be specified at all times. > > That doesn't answer my question whether the create-dhcp6 above would fail. In the current world-order, this would be ipadm create-ipv6addrs -i link0 default and it would be ok because the label would be local to the interface and IP-version. (i.e, the *-v6addrs and *-dhcp have distinct namespaces) > When ping was designed the Internet was a lot smaller and multihomed > hosts was a rare thing. > Furthermore, DNS doesn't actually return an ordered list; it returns a > set of addresses. Thus picking the first isn't defined. > >>> I can see two ways forward on that one: >>> 1. Do not allow hostnames for create-addr at all. >> >> that would be the simplest solution. I was looking at DNS as a simple >> way of creating "labels" for static addresses. >> >>> 2. Make a hostname lookup all the IPv4 and IPv6 addresses and create >>> a single object with all those addresses in it. I.e., not need for a >>> -f. > > But the alternative is to require -f everywhere i.e. I would need it > with set-addrprop, delete-address, etc. #2 seems (to me) like the better long term solution, it uses DNS as the "vanity name" for the static address. > I think a create-ipv6addrs is sufficient provided that we have to option > to add a "no-dhcpv6" or "no-stateless" address property down the road. > (Perhaps we also want to force dhcpv6 even if the RAs don't say to do > DHCPv6.) But we probably need to be able to set those properties before > in.ndpd/dhcpagent sees the newly created address object and starts > acquiring addresses. A poor-man's solution to achieve this today would be to have libipadm SIGHUP in.ndpd after feeding it the input to switch to no-dhcpv6. --Sowmini _______________________________________________ networking-discuss mailing list [email protected]
