You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In identity:node service method a hostname provided by a DHCP server is preferred over one that has been input through configuration.
I am unsure of why this decision was made, since if an operator goes into the trouble of manually configuring a hostname, it should be honored by the one given by a DHCP server.
This is only an issue, because even when a DHCP procedure is begun with a hostname provided (both with explicit ipadm-h, —reqhost argument or with ifconfig through primary flag), it does not “echo” it back properly. Instead all you get back is the hostname set to be given by default by that DHCP server.
This is observed also in OmniOS, so I am assuming this is intended behaviour.
The text was updated successfully, but these errors were encountered:
In identity:node service method a hostname provided by a DHCP server is preferred over one that has been input through configuration.
I am unsure of why this decision was made, since if an operator goes into the trouble of manually configuring a hostname, it should be honored by the one given by a DHCP server.
This is only an issue, because even when a DHCP procedure is begun with a hostname provided (both with explicit
ipadm
-h, —reqhost
argument or withifconfig
throughprimary
flag), it does not “echo” it back properly. Instead all you get back is the hostname set to be given by default by that DHCP server.This is observed also in OmniOS, so I am assuming this is intended behaviour.
The text was updated successfully, but these errors were encountered: