http://bugzilla.novell.com/show_bug.cgi?id=631116 http://bugzilla.novell.com/show_bug.cgi?id=631116#c0 Summary: Confused over which network interfaces are bridges, available Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: 64bit OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: michaelcook_mjc@yahoo.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 Using ifconfig, /etc/sysconfig/ and YAST Network Services the configuration of network interfaces doesn't seem predictable or correct on W510 laptop using XEN 4.0. Perhaps user-misunderstanding but I have the following senario of what I would like to happen and using ifconfig and YAST Network Services (apparently preferred method for XEN users on opensuse) I cannot get the configuration to work. - W510 has eth0 and wlan0 interfaces. - Two bridges are created for each interface which I use for two NICs for XEN guest Using YAST Network Services I can see I can: - provision wlan0 to be "DHCP" mode and it will attach to a wifi router and get an IP address. - provision br0 (wlan0), br1 (eth0) using "Install XEN Hypervisor Tools" This works fine, where br1 maps through to guest VM configuration file. What I want is the XEN Guest to map to a bridge which is connected to whichever NIC is up (eth0 or wlan0) and prefer eth0 if both are up. I can see I can select multiple bridge interfaces to attach br1 onto but when I attempt this I get the following error for wlan0: br1 Warning: failed to add port wlan0: can't add wlan0 to bridge br1: Operation not supported I am a bit confused why when you map a physical interface to a bridge it decides to map 0.0.0.0/32 (non-DHCP) to that physical device and then attempts to perform DHCP on the bridge (br1 in this case for eth0). Furthermore, if eth0 is disconnected while performing DHCP on br1 it 'completes' by assigning the last IP addr it saw when eth0 was connected. I dont know if this is a side-effect of failing to add wlan0 to br1 and it continues assuming DHCP is a good idea... but wlan0 ip address range isn't what ends up on br1. Mixing in XEN networking the whole picture seems to get messy and rebooting the laptop often yields a different senario (as per ifconfig output) and I can't trust YAST Network Services is doing anything sensible. Can anyone help me understand how bridges & physical interfaces are used in opensuse network management and any suggestions on XEN. What I want: - eth0 & wlan0 on br1 to map to eth0 of a VM guest I'd like ideally this all to be seamless when I switch from wlan0 to eth0 and back. The IP addrs will change but all traffic from host & guests should just get routed. I realise the DHCP of eth0 in the guest will have to update too... so its not seamless without refreshing DHCP addr assignment. Reproducible: Always Steps to Reproduce: 1. W510 laptop with opensuse 11.3 and XEN 4.0 installed 2. attempt to bridge wlan0 and eth0 to br1 with DHCP enabled 3. use ifconfig to inspect what has been assigned to bridges and interfaces Actual Results: either host traffic is directly routed to wlan0 and br1 is not useful (guest fails to route) or br1 gets old DHCP addr, routing table defaults to it (its not connected) and wlan0 is not default gw and can't route host traffic. Expected Results: a bridge can be assigned to bridge to two physical interfaces, each of which may or may not have DHCP on them. Maybe have to pick which interface to route traffic over, but physical NIC should take priority over wireless. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.