http://bugzilla.novell.com/show_bug.cgi?id=612010 http://bugzilla.novell.com/show_bug.cgi?id=612010#c0 Summary: eth0 provisioned and routes set to interface even when unplugged and overrides wlan0 Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: 64bit OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem 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.4) Gecko/20100513 SUSE/3.6.4-1.11 Firefox/3.6.4 When the laptop comes up and it has eth0 NIC and wlan0 both are provisioned. Somehow, the eth0 NIC gets an address assigned (looks like the last one it was assigned when plugged in) and the default route goes to that interface. The wlan0 which is attached to the network also gets an address but all traffic is routed to eth0. I would only expect this behaviour if eth0 was in fact up (connected) and received valid DHCP address. I dont see a network-applet on the task-bar (like I might under Ubuntu) and when I check with Yast Networking I see it is as configured as DHCP. I'm new to Yast networking but I've asked it to use ifup method as I'm trying to get XEN networking too... although this behaviour was been seen pre-XEN installation. (see dmesg/messages from this posting https://bugzilla.novell.com/show_bug.cgi?id=612006) I presently have it connected via wlan0 by ifdown eth0 and adding default route to the wlan0 interface. Wlan0 is successfully connecting and assigned a valid IP address. Reproducible: Always Steps to Reproduce: 1. start W510 laptop using suse 11.3 m7 with Intel 6000 firmware for wireless device support. 2. eth0 and wlan0 both come up, eth0 seems to be assigned an address even though not connected. 3. wait for wlan0 to be assigned an address 4. check route -n and see that default route goes to eth0 Actual Results: Routing table is pointing to eth0 interface Expected Results: whichever interface is up and using DHCP should provision the default gateway to it... in this case, eth0 is not connected, so would expect default to point to wlan0. Expect not to have to hardwire this under Network Settings in YaST because it would be more useful to automatically configure the default route based on which ever interface was in use (wired taken precedence as seen in Ubuntu). I dont think this is XEN related and would expect dom0 to still behaviour as I described. -- 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.