Bug 156376

Summary: ifup broken, dsl does not start
Product: [openSUSE] SUSE Linux 10.1 Reporter: First Name Last Name <sinderbox+novell>
Component: NetworkAssignee: Christian Zoz <zoz>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Blocker    
Priority: P5 - None    
Version: Beta 6   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log

Description First Name Last Name 2006-03-09 09:28:26 UTC
CLI is self explanatory:

server:~ # rcnetwork start dsl0
Setting up network interfaces:
    dsl0
              No configuration found for dsl0                         unused
[...]


server:~ # rcnetwork start dsl0 -o debug
CONFIG      =      <--------- PROBLEM IS HERE, it should be dsl0
INTERFACE   = dsl0
AVAILABLE_IFACES =   eth0 eth1
PHYSICAL_IFACES  =  eth0 eth1
DIALUP_IFACES    =  dsl0
TUNNEL_IFACES    =
MANDATORY_DEVICES =
SKIP             =
Setting up network interfaces:
    dsl0
              No configuration found for dsl0
    dsl0      returned 9                                              unused
[...]

Configuration exists:

server:~ # l /etc/sysconfig/network/ifcfg-dsl*
-rw-r--r-- 1 root root 202 Mar  2 17:46 /etc/sysconfig/network/ifcfg-dsl0

I solved my problem in /sbin/ifup at line 202 by setting CONFIG manualy with
if [ $INTERFACE == "dsl0" ]; then
   CONFIG=$INTERFACE
fi

It is a hack that will work only for myself, thus a proper solution is needed by the ifup maintainer. Interestingly he seems to neeed other hacks and is forcing INTERFACE manually too, just above at line 197 it reads:

# This is a workaround for bug 61387. This has to be fixed in getcfg later.
if ! is_iface_available $INTERFACE && is_iface_available $CONFIG_INTERFACE ; then
        INTERFACE=$CONFIG_INTERFACE
fi
Comment 1 Michael Gross 2006-03-09 13:29:23 UTC
I suppose this was configured with YaST, please attach the yast logfiles.
Comment 2 First Name Last Name 2006-03-09 13:57:15 UTC
errr, it was configured long ago (logs are not there anymore) with Yast and it worked up until the upgrade to beta5 (approx.). So the logs would show only a succesful configuration. I could try to do a totally new configuration in order to generate newer log files, but that will need to wait for the weekend (plz confirm if neeeded).

But since it was working and Yast nor file names were touched anymore the problem has to be somewhere else.

Commenting out my modification:

server:~ # ifup dsl0 -o debug
HWDESC = dsl0      CONFIG = dsl0      INTERFACE = dsl0
    dsl0
interface dsl0 is up
server:~ # rcnetwork stop dsl0
Shutting down network interfaces:
    dsl0
scripts/ifdown-wireless: line 630: kill: (12254) - No such process    done
server:~ # ifup dsl0 -o debug
HWDESC = dsl0      CONFIG =       INTERFACE = dsl0
    dsl0
              No configuration found for dsl0

Without analysing thewhole ifup code, my feeling is the problem has to be in the logic there. It knows the HWDESC and the INTERFACE 
but it does not find the config which has the same suffix.

server:~ # cat /etc/sysconfig/network/ifcfg-dsl0
BOOTPROTO='none'
DEVICE='eth-id-00:60:08:6f:fa:dc'
MODEM_IP='10.0.0.138'
NAME='DSL Connection'
PPPD_OPTIONS=''
PPPMODE='pppoe'
PROVIDER='provider0'
STARTMODE='auto'
UNIQUE=''
USERCONTROL='no'
VPIVCI=''

server:~ # cat /etc/sysconfig/network/providers/provider0
ASKPASSWORD='no'
AUTODNS='no'
DEFAULTROUTE='yes'
DEMAND='yes'
DSLSUPPORTED='yes'
IDLETIME='0'
IPADDR=''
ISDNSUPPORTED='no'
MODEMSUPPORTED='no'
MODIFYDNS='no'
MODIFYIP='yes'
PASSWORD='ZZZZZZZZZZ'
PHONE=''
PROVIDER='XXXXXXXXXX'
REMOTE_IPADDR=''
USERNAME='YYYYYYYYYY'
DNS1='127.0.0.1'
DNS2=''

server:~ # cat /etc/sysconfig/network/ifcfg-eth-id-00\:60\:08\:6f\:fa\:dc
BOOTPROTO='static'
BROADCAST=''
IFPLUGD_PRIORITY='20'
IPADDR=''
MTU=''
NAME='3Com 3c900 10Mbps Combo [Boomerang]'
NETMASK='255.255.255.0'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
UNIQUE='XXXXXXXXXXXXXXXX'
USERCONTROL='no'
_nm_name='bus-pci-0000:00:0a.0'
Comment 3 Michael Gross 2006-03-09 14:06:36 UTC
These sysconfig files are written by YaST, one of the configurations misses the device name, so this is not a problem with either ifup or the network scripts. We need more information about how to reproduce this or at least some logfiles on a machine this error occurred.
Comment 4 First Name Last Name 2006-03-09 14:34:23 UTC
I will reconfigure the dsl0 interface and record the Yast log files.
However these sysconfig files were written by YaST, they worked (until upgrade)
and they did not change. What the upgrade changed are probably the scripts. 

Other logs I can provide immediatelly. Yast logs will need to wait a little more.
Comment 5 First Name Last Name 2006-03-10 15:43:40 UTC
Created attachment 72297 [details]
y2log

commented my mods in /sbin/ifup
Shutted down dsl0
configure dsl0 in yast to never start
rm -r cd /var/log/YaST2/*
configure dsl1 with same data dsl0 had
copied y2log
ds11 does not start (same problem)
Comment 6 First Name Last Name 2006-03-10 15:47:00 UTC
BTW in the log states smpppd will not start.
When is it needed? Whithout it things like AUTO_RECONNECT='yes' in the provider0 file will not work?
Comment 7 Michael Gross 2006-03-13 16:43:41 UTC
Martin: Please look into this.
Comment 8 Martin Vidner 2006-03-13 16:49:22 UTC
I think Michael is wrong in comment 5.
If it worked until beta 5, it is probably a sysconfig problem. There were some getcfg changes.
Comment 9 Christian Zoz 2006-03-13 19:54:36 UTC

*** This bug has been marked as a duplicate of 157081 ***