On 10/7/20, 12:53 PM, "Linux on 390 Port on behalf of Alan Altmark" <[email protected] on behalf of [email protected]> wrote:
> I have talked up DHCP's ability to use a user ID instead of a > MAC address Option 61 (the DHCP option that allows the string option) can be any unique arbitrary string. It can be used to request information for point-to-point links that are not broadcast capable as long as there is one broadcast-capable address available to locate the DHCP server. The DHCP server gets the string and does its thing so 'mysystem-hsi1' or 'mysystem-ctc0' is a perfectly valid use of the capability. > IMO, the ease of making VM TCP/IP come up with a different configuration > file based on external criteria eliminates the need for a DHCP client. In a limited way, but why have to remember to do it or fool around with node/system name qualifiers in TCPIP CONFIG if there is a way to not have to change anything and have it Just Work AND be consistent with every other host and address management process in the whole world? Seems like one big battle we don't need to fight. It would also let you ship a completely functional TCPIP out of the box, no configuration required - just plug in the OSA, attach it to TCPIP at a predefined address and you're up and running. Think of the documentation pages saved... __ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
