Bug 586338

Summary:	openSUSE if{up,down} scripts are bloated and they work fathomless
Product:	[openSUSE] openSUSE 11.2	Reporter:	Daniel Pecka <nettezzaumanaa>
Component:	Network	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Daniel Pecka 2010-03-08 18:13:59 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8

hi suse developers ..

sorry for bothering you again with network scripts but .. eh. 

suse network scripts are unclear, complicated and works badly in 11.2 .. there are many issues like bad invoking dhcpcd via /sbin/ifup-dhcp which leads to preserving dhcpcds' own resolv.conf and so ..

issues are for example:

1) dhcp client survives after carrier removal, iface has address as is up
2) etc/resolv.conf is preserverd using strange way, so you need to manually kill dhcpcd (dhcpcd -x $iface) and run it again after carrier removal a plug in again
3) dhcp client is invoked for all iface at startup even if there is no link
4) rc scripts produces errors while waiting for *mandatory devices
5) at least ipv6 on/off switch in yast doesn't work ..

i think that these scripts need a general maintenance and refresh ..

Reproducible: Always

Steps to Reproduce:
1. don't use NM
2. take a closer look at how traditional network stack in suse works
3. simply put a "set -x; exec 2>/tmp/dhcp-$$.log" at beginning of /sbin/ifup-dhcp and take a look which all nonsenses and fathomless things script does and probes
Actual Results:  
i please a network maintainers in openSUSE to don't scratch this BUG with poor putoff that we have to use a NM if we want our netstack working reasonable way ..

have a nice day and regards ..

ave, daniel

Comment 1 Marius Tomaschewski 2010-03-09 10:29:12 UTC

First of all:
yes, the scripts grown over the years and are bloated trying to catch
many corner cases. I'm working on the cleanup when my time permits ...
a lot of this time goes into bug reports that aren't any.

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8)
> Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8
> 
> hi suse developers ..
> 
> sorry for bothering you again with network scripts but .. eh. 
> 
> suse network scripts are unclear, complicated and works badly in 11.2 .. there
> are many issues like bad invoking dhcpcd via /sbin/ifup-dhcp which leads to
> preserving dhcpcds' own resolv.conf and so ..
> 
> issues are for example:
> 
> 1) dhcp client survives after carrier removal, iface has address as is up

Change from "At Boot Time" to "On Cable Connection" in yast2 network
or manually set

   STARTMODE="ifplugd"

in the ifcfg files.
When you have multiple interfaces as wireless and wired, then set also
IFPLUGD_PRIORITY, using higher number for the preferred link and lower
number to the another, e.g.: 10 for wireless and 20 for wired ethernet;
it will cause that wired link is used when carrier is there, otherwise
wireless.

> 2) etc/resolv.conf is preserverd using strange way, so you need to
> manually kill dhcpcd (dhcpcd -x $iface) and run it again after
> carrier removal a plug in again

This is not needed in above case, when ifplugd is used.

You also don't need to kill dhcpcd manually. Calling the ifdown-dhcp
script directly should do it for you. Also "rcnetwork restart eth0".

> 3) dhcp client is invoked for all iface at startup even if there is no link

In STARTMODE=onboot (auto), yes. See above. You can set STARTMODE=ifplugd.

> 4) rc scripts produces errors while waiting for *mandatory devices

See above. You can also disable / change this: adjust MANDATORY_DEVICES
and/or the WAIT_FOR_INTERFACES variables in network/config.

> 5) at least ipv6 on/off switch in yast doesn't work ..

Different problem => yast2 network. See bug 558020 - disable ipv6 in YaST2.

It is also the only true problem that I see here. 1...4 are caused by the
configuration / missed link monitoring. It would be also possible to enable
the ifplugd on ethernet interfaces by default (in some cases it is enabled
by default, except when the interface is used as bridge port? only when a
wireless interface is there/configured?). Feel free to open an enhancement
request bug or fate for yast2-network on 11.3.

I reassign to the yast2-network maintainer, because of disable_ipv6.

Comment 2 Michal Zugec 2010-03-15 13:53:58 UTC

Issues 1-3 are about ifplugd, which is duplicate of bnc#586376

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