[sles-beta] network settings for SLES12 installation

Eugen Block eblock at nde.ag
Wed Nov 25 08:31:11 MST 2015


Hi Steffen,

> I agree that 'netsetup' in sle12 is not perfect either. So if you
> go ahead and make a bugreport, I will look into this for sp2.

It was more a question of how it is designed to be used than a  
potential bug report. Thanks for clearing that up, it helps me a lot!

> The network config is always copied to the target system.

I ran another test with SLE12-GMC using the ifcfg syntax, you are  
absolutely right about the VMs configuration, I find all the values I  
provided. What I didn't find - and that must be the part which let me  
write that statement about not storing the network settings - is the  
complete network configuration in the autoinst.xml which is created  
automatically after the installation. I saw only the ip address and  
the netmask, the gateway, nameserver and domain were not included (I  
only used these parameters). I guess this refers to your statement "as  
linuxrc is fine setting up a network based on just the ip and netmask"?

Then I ran another test with the GMC2, and in that autoinst.xml the  
gateway is included, but still no hostname or nameserver. Is there a  
reason for that?

Regards,
Eugen


Zitat von Steffen Winterfeldt <snwint at suse.de>:

> Hi Eugen,
>
> On Tuesday 2015-11-24 12:58, Eugen Block wrote:
>
>> I have a question regarding the installation process of SLES12  
>> since SP0. I use virt-manager on a Xen host running on SLES11-SP3,  
>> but my question also refers to installing xen-guests directly via  
>> config files.
>> If I wanted to avoid network setup via dhcp on SLES11 VMs I used  
>> the "Additional Arguments" in virt-manager, in the xen-config file  
>> it is the "extra" line, where I used to provide information like  
>> "Netsetup=-dhcp,all Hostname=<HOSTNAME> Domain=<DOMAIN> Hostip=<IP>  
>> Nameserver=<NAMESERVER> Gateway=<GW>".
>> If I use the same syntax with SLES12-SP0/SP1-RC2/SP1-RC3/SP1-GMC, I  
>> always get into the linuxrc confirmation screen where all my  
>> entries are preselected (see the attached screenshot), I just have  
>> to confirm them. So somehow linuxrc knows what it is, but why do I  
>> have to confirm it?
>
> The original plan is/was for netsetup to provide network setup dialogs. Like
> netsetup=hostip,gateway should show two popups asking for hostip and gateway.
> Likewise netsetup=-dhcp would just skip the question about dhcp usage.
>
> What it actually does in sle11 is to show popups only if it thinks  
> some data is
> still needed. So netsetup=-dhcp hostip=10.10.0.1/16 will not ask for  
> gateway or
> nameserver (as it should) as linuxrc is fine setting up a network  
> based on just
> the ip and netmask.
>
> The 'all' was just a hack making netsetup=dhcp,all run dhcp on all  
> interfaces.
>
> All in all the network config syntax was not in a good shape up to sle11.
>
> So there is now in sle12 the 'ifcfg' option which lets you specify exactly
> what you want to go into the ifcfg files without getting the linuxrc
> guesswork in the way.
>
> That said, I agree that 'netsetup' in sle12 is not perfect either. So if you
> go ahead and make a bugreport, I will look into this for sp2.
>
>> My colleage helped me and found a syntax where linuxrc doesn't ask  
>> for this confirmation, but then the settings I have provided aren't  
>> stored anywhere. So
>
> The network config is always copied to the target system.
>
>
> Steffen
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta


-- 
Eugen Block                             voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG      fax     : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg                         e-mail  : eblock at nde.ag

         Vorsitzende des Aufsichtsrates: Angelika Mozdzen
           Sitz und Registergericht: Hamburg, HRB 90934
                   Vorstand: Jens-U. Mozdzen
                    USt-IdNr. DE 814 013 983



More information about the sles-beta mailing list