SuSE 9.3 dhcp server config
Hi,
I want to install a DHCP server using autoyast over a network connection.
The dhcp-server section of my control file looks like this:
<?xml version="1.0"?>
<dhcp-server xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude">
To correct myself: On Thu, 9 Jun 2005, Volkmar Glauche wrote:
Now, when I install, everything is fine (control file ok, network up and running...), but the autoconfiguration module for the dhcp server fires up a message box stating "No network interface found..." and a message that YaST will stop now. When I hit OK, then autoinstallation continues and dhcp gets set up properly.
The sysconfig entries are not written by the YaST module, and the service is not linked into the corresponding runlevels. -- Volkmar Glauche - Department of Neurology volkmar.glauche@uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg
On Thu, Jun 09, 2005 at 08:41:31AM +0200, Volkmar Glauche wrote:
Hi, I want to install a DHCP server using autoyast over a network connection. The dhcp-server section of my control file looks like this: <?xml version="1.0"?> <dhcp-server xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns:xinclude="http://www.w3.org/2001/XInclude">
<chroot>1</chroot> eth0 1 0 </dhcp-server> The dhcpd.conf comes from elsewhere, since it is a quite complicated setup on replicated machines (although YaST2 did quite a good job in translating the external source into an xml config). Now, when I install, everything is fine (control file ok, network up and running...), but the autoconfiguration module for the dhcp server fires up a message box stating "No network interface found..." and a message that YaST will stop now. When I hit OK, then autoinstallation continues and dhcp gets set up properly.[...] A workaround would be to set the sysconfig variables directly and add the service start to a <runlevel> section. Any other ideas?
Hi Volkmar, most likely it is a bug causing that the DHCP server module runs before the networking module and thus at that time there is no interface configured. You can check the logs whether that is the case. (https://bugzilla.novell.com/show_bug.cgi?id=78575) If you can modify yast2-dhcp-server.rpm in the installation source, solve it by adding "X-SuSE-YaST-AutoInstRequires=lan" to dhcp-server.desktop -- Martin Vidner, YaST developer SuSE CR, s.r.o. e-mail: mvidner@suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz
participants (2)
-
Martin Vidner
-
Volkmar Glauche