https://bugzilla.novell.com/show_bug.cgi?id=750328 https://bugzilla.novell.com/show_bug.cgi?id=750328#c0 Summary: Network Manager (KDE) with two default gateways available Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dfreeman@ieee.org QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Using KDE and Network Manager. Connect to a network that supplies a default gatway using DHCP. Connect to another network that also supplies a default gateway. However this gateway is having problems and is not a viable route to the outside world. There are still desirable resources on the network, but a failed gateway is being supplied by DHCP. Under this scenario, there is no access to the outside world, even though the first network supplies a working gateway. The user is surprised to have less connectivity after plugging in an extra cable. You can work around this by reconnecting to the first network, but in a situation where cables are being unplugged or wireless is dropping out, you keep finding yourself without a connection to the outside world. Or, you can note the IP address you got from DHCP, and change to a fixed IP address configuration. Until your lease expires and you clash with someone else, having alredy forgotten what you did. This is a bug as long as I can't disable the setting of the gateway by DHCP on one of the connections. I still want to obtain an IP address, but not interfere with the good gateway from the other network. Similarly this should apply to the nameservers if they can't safely coexist with the ones from the other network. Also, as a feature request, I would like to be able to set one of my connections, either by the name of the connection or by the interface that I use to connect, as having the dominant gateway. That way, even if I have two that work, I can select the most secure, most reliable, fastest, or least costly to use (i.e. dollar value). Then, when this connection drops out, the other gateway should be immediately added to the kernel routing table. The above suggestions regarding disabling certain DHCP parameters would be unnecessary if I could set one connection as dominant. Reproducible: Always Steps to Reproduce: 1. Connect to a network using Network Manager, with DHCP 2. Connect to another network using DHCP. This one has a bad gateway 3. Actual Results: Connectivity is lost as the bad gateway displaces the good one. Expected Results: Automatically fail back to the other gateway when the dominant one no longer forwards packets. -- 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.