https://bugzilla.novell.com/show_bug.cgi?id=450303 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450303#c1 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |hwit@a-domani.nl --- Comment #1 from Marius Tomaschewski 2008-12-01 08:46:39 MST --- Hmm... strange. You are using xen setup and there is a eth0 interface used and not a bridge with eth0 as a bridge port? Can you attach the /etc/sysconfig/network/ifcfg-* files (except ifcfg-lo) and the output of "ip addr show" at a time before your ifconfig calls? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450303 User hwit@a-domani.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=450303#c3 --- Comment #3 from Hans Witvliet 2008-12-01 13:55:04 MST --- Indeed strange, Didn't cone as far as testing xen-part, because of this situation (and the pile of other systems i had to upgrade on patch-day, our last friday of the month). Probably a combination of things at my end, as something this seriously would have been detected by many others before.... Will be back at work tomorrow to get any config files (Can not login onto DoD network online ;-) Yes, i tried pinging with address (obviously, while network is down, no name resolving could be done....) Test were done on HP's DL320-g2 and DL360-G4 The noisy type of servers that don't have wifi I thought i mention it because of the intel-saga ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450303 User hwit@a-domani.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=450303#c5 --- Comment #5 from Hans Witvliet 2008-12-04 02:16:28 MST --- 1) If, at the grub-prompt i choose for normal kernel instead of XEN, the problem still exists. So it looks like it's not xen-related 2) after booting (kmp/xen), while network seems dead, the cable is unplugged and plugged again, no changes (nothing from if-up-scripts or udev) Next wil follow requested files in two tgz.

From kc0008 (installed manually, from local install server) attachement 1 contains: boot.msg ifcfg-br0 ifcfg-eth0 ifcfg-eth1 lastlog localmessages messages resolv.conf uname.out warn xinetd.log

From kc0007 (installed my means of autoyast-file and local install server) boot.msg ifcfg-br0 ifcfg-eth1 ip_addr_show.txt lastlog messages ping2.out resolv.conf warn ethtool.out ifcfg-eth0 ifconfig.out iptables.out localmessages ping.out ping3.out tcpdump.out xinetd.log

Third attachement contains the XML-file used for building the system, -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450303 User hwit@a-domani.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=450303#c7 --- Comment #7 from Hans Witvliet 2008-12-09 15:01:47 MST --- Created an attachment (id=259050) --> (https://bugzilla.novell.com/attachment.cgi?id=259050) tar with files described previously -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450303 User hwit@a-domani.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=450303#c9 --- Comment #9 from Hans Witvliet 2008-12-09 15:03:50 MST --- Created an attachment (id=259052) --> (https://bugzilla.novell.com/attachment.cgi?id=259052) xml-file from kc0008, used to install kc0007 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450303 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450303#c11 --- Comment #11 from Marius Tomaschewski 2008-12-10 06:31:39 MST --- (In reply to comment #10 from Hans Witvliet)

Something went wrong with the attachments....

As you pointed out, system uses dhcp, so the device br0 also got automagically the "dhcp" option.

This is ok. The bridge interface gets the IP or DHCP now, ethX is only a bridge port.

Modified the startup to manually. Looks like to work, but that should not be the solution.

?? As far as I see, it is only needed to fix the ifcfg-eth0 file to use BOOTPROTO='none'. Since you don't use any bridge (br1) for eth1, you can start the dhclient there.

btw, the br0-device, is that new in 11.1? In 10.3 (and older) the bridges for xen were named xenbr0, xenbr1,... In 11.0 the bridges were named eth0, eth1, eth2

Yes, there was a network-bridge script that was renaming the interfaces and breaking 50% of the configurations. Then the user called "rcnetwork restart" and 100% of configurations was broken.

And they were created not at network-startup, but after/during the startup of xend, by meanes of the routines in /etc/xen/scripts.

Yes, the bridges are created correctly as ifcfg files now and are used with xen as well as with normal kernel.

Should i get rid of br0 and use the old xen-scripts instead?

This is up to you => unsupported system.

(And what is the use of the br0-bridge, if the system is NOT doing XEN? )

Xen is not the only software using them, there is also kvm and virtualbox at least. As soon as one of them is installed, bridges are created by default. Resolving to WORKSFORME - the configuration is broken. Please use the most recent sysconfig & dhcpcd from factory (or 11.1 final). That the br0 gets started in the remotefs flow a second time should be fixed: * Mi Nov 26 2008 mt@suse.de - Fixed rcnetwork remotefs virtual iface start order (bnc#447098). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.