>>
>> Static/autoconf IPv6 addresses are still under discussion. In theory,
>> the *-addr commands above should continue to just be usable for static
>> IPv6.
>> (The context of the address would tell us if ipv4 or ipv6 was implied,
>> except when dns was invoked, e.g., ipadm create-addr link0/myhost.com,
>> for which case we can have a -f flag, or some clearly defined
>> defaults).
>
> What is the name of the object created using link0/myhost.com i.e., what
> name would I use with set-addrprop and delete?
> If I can have two (-f inet link0/myhost.com, and -f inet6
> link0/myhost.com), then wouldn't you need '-f' to become part of the name?
>
> Furthermore, if myhost.com resolves to >1 IPv4 addresses (or IPv6
> addresses), does the above create a single address object with N
> addresses in it?
>
> I can see two ways forward on that one:
> 1. Do not allow hostnames for create-addr at all.
> 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.
In case [2] above how will we be able to apply 'address' properties
specific to v4 or v6 addresses.
Can we consider creating address using hostname as a special case of
assigning static addresses to an interface?
Once we have done that, we can individually refer the address using the
tuple <interface, address>, which is the same tuple used to identify
'statically' added addresses.
for eg:
#ipadm create-addr -i bge1 hostname
--> it returned 2 v4 addresses and 1 v6 address (v4addr1,
v4addr2, v6addr1)
#ipadm show-addr
--> displays all the addresses just assigned to the interface
#ipadm set-addrprop -i bge1 -p <prop>=<val> v4addr1
--> sets the property on v4addr1.
similarly we could do it for other addresses.
For deletion, we select individual addresses using the tuple.
Above should work, right?
~Girish
