Bug 219395

Summary:	use of PERSISTENT_NAME in ifcfg-br0 to configure bridge
Product:	[openSUSE] openSUSE 10.3	Reporter:	Diego Ercolani <diego.ercolani>
Component:	Network	Assignee:	Christian Zoz <zoz>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	32bit
OS:	All
Whiteboard:
Found By:	Integration Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Diego Ercolani 2006-11-09 14:23:27 UTC

whithin the ifcfg-br0 is it possible to use PERSISTENT_NAME='name' to create the bridge virtual interface name instead of default brX name but there are some issues in the startup script /sbin/ifup during system startup because it have to restart network to bring up bridge interface

Comment 1 Christian Zoz 2006-11-14 14:48:14 UTC

What issues?

Can it be related to bug 193216?

Comment 2 Diego Ercolani 2006-11-14 15:14:28 UTC

I'm not allowed to see 193216

Comment 3 Christian Zoz 2006-11-14 15:41:03 UTC

Can you see it now?

Comment 4 Diego Ercolani 2006-11-14 15:58:04 UTC

yes, but with my installation bridge starts at boot!
I'm going to explain, I hope....
OpenSUSE version is 10.2Beta1+ (current developing) or better, was installed October 6 2006).
Only if I use PERSISTENT_NAME bridge have to be restarted maually after boot-up. I give you my WORKING ifcfg-br0 configuration /etc/sysconfig/network/ifcfg-br0:
STARTMODE='auto'
BOOTPROTO='static'
IPADDR='192.168.10.99'
NETMASK='255.255.255.0'
BROADCAST='192.168.10.255'
BRIDGE='yes'
BRIDGE_PORTPRIORITIES='50 20'
DHCLIENT_WAIT_AT_BOOT=30
BRIDGE_PORTS='eth-id-00:0d:88:2e:74:a1 eth-id-00:15:e9:f1:ad:54'
#PERSISTENT_NAME=examplename

and ethernet configurations ifcfg-eth-id-00:0d:88:2e:74:a1:
BOOTPROTO='dhcp'
UNIQUE='rBUF.g1Ba_umQFy6'
STARTMODE='off'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'

ifcfg-eth-id-00:15:e9:f1:ad:54:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='D-Link DFE-538TX 10/100 Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='off'
UNIQUE='JNkJ.g1Ba_umQFy6'
USERCONTROL='no'
_nm_name='bus-pci-0000:00:10.0'

If I remove the '#' before PERSISTENT_NAME definition, the bootup process doesn't configure the bridge.

Comment 5 Christian Zoz 2006-11-20 18:55:53 UTC

PERSISTENT_NAME was never intended for virtual interfaces like bridge interfaces. And since we provide persistent interface names via udev rules now, PERSISTENT_NAME is obsolete (just there for backward compliance).

Nevertheless i will have a look at it. But not for 10.2.

Comment 6 Diego Ercolani 2006-11-21 08:49:15 UTC

Ok. Is it possile to add for 10.2 a warning/error message so people doesn't use it?

something like.....
[ -z "$PERSISTENT_NAME" ] || echo "Warning/Error PERSISTENT_NAME not allowed for virtual interfaces, please see /usr/share/doc....."

thank you
Diego

Comment 7 Christian Zoz 2007-07-26 16:19:42 UTC

I dropped PERSISTENT_NAME completely. For physical interfaces there is /etc/udev/rules/{70,75}*net*rules. And some virtual interfaces like bridges or bonding interfaces can just use the wanted name as configuration name.
If you create a bridge config file ifcfg-mybridge you may call then just ifup/down mybridge. It will also be set up at boot time.

Try 10.3 Alpha 7 as soon as available.