Feature changed by: Juergen Weigert (jnweiger) Feature #300323, revision 40 Title: Preset network configuration using values from DHCP openSUSE-10.2: Rejected by Jiri Srain (jsrain) reject date: 2006-09-19 16:25:11 reject reason: Sorry, not enough resources, postponing for 10.3. Priority Requester: Desirable Projectmanager: Neutral openSUSE-10.3: Rejected by Stanislav Visnovsky (visnov) reject date: 2007-07-26 16:25:15 reject reason: Needs more research. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.0: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-04-01 13:32:27 reject reason: Clearly a server-only feature. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.2: Rejected by Michael Löffler (michl19) reject date: 2009-01-09 14:15:37 reject reason: As it is not done now for 3 years and just "desirable" for everybody I reject this for 11.2 Priority Requester: Desirable Requested by: Glen Davis (gldavis) Description: During the SLES install, it would be nice to have a dhcp client piece that could pick up information from a DHCP server and autofill that information into the appropriate fields during the install. Fields such as Mask, Router, DNS servers on the networking screens, and also SLP and NTP time information on the OES install screens. Netware has a similiar feature that fills in much of this informaton ( I believe written by Sheffer Clark) and it would be nice to have this same infomration auto populated in the Yast install. References: Original report (https://bugzilla.novell.com/show_bug.cgi?id=115013) Why not do it (https://bugzilla.novell.com/show_bug.cgi?id=46369) + Documentation Impact: + ? Discussion: #1: Martin Vidner (mvidner) (2006-01-10 10:57:59) Sorry, no. If the addresses are managed by a DHCP server, then we must not take one of them and use it statically because tomorrow the server can assign it to someone else. See bug 46369. Why don't you simply use DHCP in all cases? #2: Glen Davis (gldavis) (2006-01-10 16:27:22) Understood, do not get the ipaddress, but we could get the mask, router, dns server, slp server, and ntp server. Maybe we just have a check box that asks for lookup from DHCP. The fields of course could always be changed from what the dhcp server provides. #3: Stanislav Visnovsky (visnov) (2006-08-29 08:59:18) We should offer this method as another automatic option to fill the defaults, similar to SLP in other parts of the configuration. #4: Stanislav Visnovsky (visnov) (2006-08-29 09:00:08) From mail by Sheffer Clark: There is a DHCP client module (I forget the exact name) on NetWare that uses a DHCP Inform to collect the information. I have worked on the DHCP module on NetWare, but do not work on this module. However, a few months ago I did a little experimenting with the DHCP client (dhcpd). If the server can temporarily allocated a DHCP address, the current client lease file will contain this info. The dhclient.conf file can be configured request other options as well. The client lease file can be a bit difficult to find and the some complex options may not be correctly parsed, like SLP; it would be best if the raw option info for the current lease could be requested directly from the DHCP daemon. I don't know of this will help you, but it may be of some worth. I do know that the Novell Linux client group could also like to be able collect SLP server and scope info using a DHCP Inform. You might want to enlist their help. #5: Lars Müller (lmuelle) (2007-06-11 15:33:24) See FATE #100250 why the NTP configuration on a DHCP configured network should not be stored statically in ntp.conf and how this could be done for a DHCP driven setup. #6: Jiri Srain (jsrain) (2007-07-26 13:44:45) Please, postpone. We need to do research on how to get the information from DHCP first. #7: Jiri Srain (jsrain) (2008-03-19 15:13:15) Marius, Peter, which way do you suggest to get the information? Do you find output of dhcpcd-test (for configuring individual interface), resp, dhcpcd-test for all interfaces for configuring services an appropriate way? #8: Peter Poeml (poeml) (2008-03-28 15:10:07) (reply to #7) I no longer take care of DHCP. #9: Peter Poeml (poeml) (2008-03-28 15:13:55) (reply to #8) Please remove me from "needinfo". Thanks! #10: Marius Tomaschewski (mtomaschewski) (2008-03-31 09:15:04) (reply to #7) Yes, using dhcpcd-test sounds fine, although I'm not sure if it is a good idea to store something. Note, that when the dhcp clients was started in a non-test mode, they write the informations into a lease / cache file and use them after a reboot in case the server is not available. -- openSUSE Feature: https://features.opensuse.org/300323