Bug 106836

Summary: unusable network proposal when pppoe is detected; it always is
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Christoph Thiel <cthiel>
Component: InstallationAssignee: Martin Vidner <mvidner>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Blocker    
Priority: P5 - None CC: adrian.schroeter, aj, ke, mvidner, ro
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /var/log/YaST2/*

Description Christoph Thiel 2005-08-23 19:44:38 UTC
YaST2 did not manage to create a working network configuration in beta3-pre. It
said something like "Network configured" in the proposal, but the configuration
was just static without any ip address set. DHCP should have been the default
configuration...

I´ll attach y2logs soon.
Comment 1 Christoph Thiel 2005-08-23 19:45:10 UTC
Created attachment 47279 [details]
/var/log/YaST2/*
Comment 2 Martin Vidner 2005-08-23 20:39:08 UTC
*** Bug 73692 has been marked as a duplicate of this bug. ***
Comment 3 Martin Vidner 2005-08-23 20:49:11 UTC
It only occurs when you have a PPPoE device that you leave unconfigured.
A workaround is to configure the PPPoE device or to configure the NIC.
So I am downgrading.

Possible solutions:
A) use a new text "Configured without an address", maybe + " (for PPPoE)"
B) turn off proposing to set up a NIC w/o address. I would have to look deeper
whether it would not disable configuring PPPoE at that stage.
Comment 4 Andreas Jaeger 2005-08-24 04:42:07 UTC
AFAIK this happened during a default installation.  There's no PPPOE device
connected.  I'll double check in an hour with a default installation to see
whether this is really the case.
Comment 6 Martin Vidner 2005-08-24 08:30:54 UTC
Yast uses SCR::Read (.probe.pppoe) which is mapped to hwinfo --pppoe. In Beta  
3 that gives almost the same output as hwinfo --network which looks suspicious  
to me. (Note that unfortunately I don't know how a valid output of hwinfo  
--pppoe should look like. The code simply checks whether the list it got is  
empty.)  
In Beta2 (f33.suse.de), hwinfo --pppoe returns nothing.  
IIRC pppoe probing is done via network traffic so I had suspected a stray  
pppoe server on the network but the actual probes seem to indicate that hwinfo  
misdetects it. Arvin am I right?  
 
Comment 7 Steffen Winterfeldt 2005-08-24 08:36:40 UTC
I need a machine with dsl to test this. 
 
What are you doing --pppoe for anyway? It doesn't return anything useful 
even _if_ it would work. Why don't you use --dsl? 
Comment 8 Christoph Thiel 2005-08-24 08:38:54 UTC
Martin? 
Comment 9 Arvin Schnell 2005-08-24 08:42:17 UTC
Yes, something has changed:

On 9.3 hwinfo --pppoe was simply empty when no pppoe server was found.
When a pppoe server was found hwinfo listed the network interface and
included a line "Features: PPPOE".

As it seems on Beta 3 hwinfo --pppoe always lists all interfaces and
included the line "Features: PPPOE" on the one where the pppoe server
was found.
Comment 10 Steffen Winterfeldt 2005-08-24 08:52:38 UTC
fixed in hwinfo 11.15 
Comment 11 Martin Vidner 2005-08-24 09:04:27 UTC
Arvin, I see something slightly different: 
.probe.pppoe returns all interfaces and marks one as pppoe whereas hwinfo 
--pppoe returns all interfaces and says nothing else about pppoe. I hope that 
the fix des the right thing. 
 
f213.suse.de: 
linux:~ # echo '`Read (.probe.pppoe)' |/usr/lib/YaST2/bin/y2base stdio scr  
([]) 
([$["bus":"None", "bus_hwcfg":"none", "class_id":263, 
"dev_name":"eth0", "dev_names":["eth0"], "driver":"8139too", 
"model":"Ethernet network interface", "old_unique_key":"lJko.ndpeucax6V1", 
"pppoe":true, "resource":$["hwaddr":[$["addr":"00:11:5b:22:c0:97"]], 
^^^ 
"link":[$["state":true]]], "sub_class_id":1, 
"unique_key":"usDW.ndpeucax6V1"], 
$["bus":"None", "bus_hwcfg":"none", 
"class_id":263, "dev_name":"lo", "dev_names":["lo"], "model":"Loopback 
network interface", "old_unique_key":"qtiw.GQNx7L4uPNA", 
"resource":$["link":[$["state":true]]], "sub_class_id":0, 
"unique_key":"ZsBS.GQNx7L4uPNA"], 
$["bus":"None", "bus_hwcfg":"none", 
"class_id":263, "dev_name":"sit0", "dev_names":["sit0"], "model":"Network 
Interface", "old_unique_key":"Shbg.nfEXJulusj6", "sub_class_id":129, 
"unique_key":"wl2P.nfEXJulusj6"]]) 
 
linux:~ # hwinfo --pppoe 
01: None 00.0: 10701 Ethernet 
  [Created at net.111] 
  Unique ID: usDW.ndpeucax6V1 
  SysFS ID: /class/net/eth0 
  SysFS Device Link: /devices/pci0000:00/0000:00:0e.0 
  Hardware Class: network interface 
  Model: "Ethernet network interface" 
  Driver: "8139too" 
  Device File: eth0 
  HW Address: 00:11:5b:22:c0:97 
  Link detected: yes 
  Config Status: cfg=no, avail=yes, need=no, active=unknown 
 
02: None 00.0: 10700 Loopback 
  [Created at net.111] 
  Unique ID: ZsBS.GQNx7L4uPNA 
  SysFS ID: /class/net/lo 
  Hardware Class: network interface 
  Model: "Loopback network interface" 
  Device File: lo 
  Link detected: yes 
  Config Status: cfg=no, avail=yes, need=no, active=unknown 
 
03: None 00.0: 10781 Network Interface 
  [Created at net.111] 
  Unique ID: wl2P.nfEXJulusj6 
  SysFS ID: /class/net/sit0 
  Hardware Class: network interface 
  Model: "Network Interface" 
  Device File: sit0 
  Config Status: cfg=no, avail=yes, need=no, active=unknown 
 
For the record, the discussion about the original feature request is in bug 
38662. 
Comment 12 Arvin Schnell 2005-08-24 09:35:46 UTC
With hwinfo 11.14 I only see the "pppoe":true when I have my pppoe
server turned on.  I check what hwinfo 11.15 does.
Comment 13 Arvin Schnell 2005-08-24 09:53:46 UTC
hwinfo version 11.15 returns only the interfaces with feature pppoe.
So SCR::Read (.probe.pppoe) returns an empty list if no pppoe server
was detected:

linux:~ # rpm -q hwinfo
hwinfo-11.15-2
linux:~ # hwinfo --pppoe
linux:~ # echo '`Read (.probe.pppoe)' | /usr/lib/YaST2/bin/y2base stdio scr
([])
([])
linux:~ #