final configuration brings down eth0
For some reason my eth0 is being brought down at the end of configuration during the execution of /usr/lib/YaST2/bin/YaST2. Before that script has run eth0 is up, and afterwards it is down. I have taken all network configuration out of my xml control file, and no ifcfg-eth file appears in my /etc/ sysconfig/network directory so I don't know why it stops working. After rebooting eth0 works fine as our kernel looks after eth0 itself. thanks for you help, brian
On Tue, Feb 08, 2005 at 07:37:52PM -0800, Brian Corriveau wrote:
For some reason my eth0 is being brought down at the end of configuration during the execution of /usr/lib/YaST2/bin/YaST2. Before that script has run eth0 is up, and afterwards it is down. I have taken all network configuration out of my xml control file, and no ifcfg-eth file appears in my /etc/ sysconfig/network directory so I don't know why it stops working. After rebooting eth0 works fine as our kernel looks after eth0 itself.
Hi Brian, at the end, /usr/lib/YaST2/bin/YaST2.firstboot (which is a wrapper around .../YaST2) stops all network interfaces *if* you have installed using VNC or SSH. It is expected that later /etc/init.d/network start will bring the necessary interfaces up. -- Martin Vidner, 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
Hi Martin. I'm not using VNC or SSH, and my eth1 and lo interfaces were staying up. Only eth0 was being brought down. I actually did some manual executing of scripts to figure out that it was the YaST2 script during the last bit of configuration where eth0 was disappearing, before getting back to the wrapper script. I checked the y2logs and saw that eth0 was being touched: y2log:2005-02-09 16:00:36 <1> linux(4105) [YCP] clients/inst_netsetup.ycp:51 Output: $["exit":0, "stderr":"", "stdout":"eth0\n"] y2log:2005-02-09 16:00:36 <1> linux(4105) [YCP] clients/inst_netsetup.ycp:56 Updated netdevice: eth0 (eth0) y2log:2005-02-09 16:00:36 <1> linux(4105) [YCP] clients/inst_netsetup.ycp:103 Setting up device: /sbin/ifconfig eth0 up 11.15.254.244 netmask 255.128.0.0 I figured out that in inst_netsetup.ycp there is a ycp function called do_network_setup(). It checks for TEST, VNC, SSH and returns false if those are set, which seems to be exactly what I want. I added a script to run after installing the rpms to change the function to always return false and now my eth0 stays up. It would be good if a standard option or xml config could keep autoyast from doing anything with the network setup, especially for specialized or embedded systems. thanks brian
Hi Brian,
at the end, /usr/lib/YaST2/bin/YaST2.firstboot (which is a wrapper around .../YaST2) stops all network interfaces *if* you have installed using VNC or SSH. It is expected that later /etc/init.d/network start will bring the necessary interfaces up.
participants (2)
-
Brian Corriveau -
Martin Vidner