https://bugzilla.novell.com/show_bug.cgi?id=385683 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |tambet@novell.com -- 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=385683 User ajorgensen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c2 Andrew Jorgensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #2 from Andrew Jorgensen 2008-05-12 11:08:27 MST --- No, there's still a problem here. Suppose I am connected to wireless and I connect to another machine using a crossover cable. Since wired is faster it would set the default route to wired even though I can only connect to one machine in that case. It's also really annoying to have my machine connect to both my wired and wireless networks at home even though they are the same network. Until there is UI to control the multiple device behavior NM should default to using only a single device. -- 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=385683 User ajorgensen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c4 Andrew Jorgensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #4 from Andrew Jorgensen 2008-05-12 13:11:43 MST --- But I do want it to connect automatically, I just don't want it to connect automatically when I am already connected to the wired network. What are the use-cases for multiple device support? Connect to the Internet by two means Connect to the Internet by one means and to a private network by another Share Internet from one connection to another Of those use cases only the first is covered at all by routing over the faster link. The second is only covered in the case where the wired network happens to be the route to the Internet. The third is not yet covered at all and the fastest link solution has the same problem here as the second use case has. The first use case is the least common / least important because only one connection is needed at any given time if both are merely to get to the Internet. The first use case may also cause a bug where either NM will send notifications to listeners saying that a connection has been taken down when really we're still connected to the Internet or, more likely, will not tell listeners that the connection they were routing over has just gone down. Maybe that's already been worked out. Are there other use cases I didn't list here? NM must default to single-device behavior unless the user requests it to connect to multiple devices. The fact that multiple-device support is an oft-requested feature means that people want to be able to control that feature. It means they want to use it for specific use-cases where it makes sense to use it. The feature as it exists right now does not fill that need and causes confusion and frustration for less experienced (and even more experienced) users. -- 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=385683 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c6 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #6 from Tambet Ingo 2008-10-13 00:23:17 MDT --- Let's try once again. "For example, I was connected to my wireless network and plugged in to my wired network so that I could transfer some large files. The transfer didn't get any faster, though, because it was routing over wireless anyway." Fixed in 11.1 beta3. "Suppose I am connected to wireless and I connect to another machine using a crossover cable. Since wired is faster it would set the default route to wired even though I can only connect to one machine in that case." The default route is configured by you or your DHCP server. The other machine should not return you a default route and NM will not make one up. "It's also really annoying to have my machine connect to both my wired and wireless networks at home even though they are the same network." It's really annoying that all your open TCP connections die when you decide you need faster transfer and plug in ethernet cable to make it faster. "I can confirm it doesn't still as of OpenSuSE 11.1 beta 3." No, you can not. beta3 isn't released yet. "And yes, it's very annoying." And yes, it's very annoying to keep closing a bug only to get it reopened again. One more time: THIS IS NOT A BUG, IT'S THE DESIGNED BEHAVIOR. If you don't like it, go convince the NM maintainer on NM list. -- 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=385683 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c9 --- Comment #9 from Tambet Ingo 2008-10-13 08:53:31 MDT --- I give up. Let's have this bug open forever. -- 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=385683 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c11 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #11 from Tambet Ingo 2008-10-13 09:22:57 MDT --- Commenting the use cases from comment #4 "Connect to the Internet by two means" Not sure why you listed that as I am looking for use cases that do not work. "Connect to the Internet by one means and to a private network by another" Supported. Just configure your connections correctly, especially, make sure the default route property is set correctly. Find the "Routes" button from the connection editor to even work around incorrectly configured DHCP servers. "Share Internet from one connection to another" Supported. Go to connection editor -> edit connection -> IP4 setting tab and select "Shared to other computers". I believe I have commented all the examples and use cases listed here and shown how each one can be achieved. I marked the bug as FIXED because I fixed the issue described at the original report (and mentioned it in my comment). If anyone has any more use cases, feel free to share them. -- 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=385683 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c13 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |ajorgensen@novell.com --- Comment #13 from Tambet Ingo 2008-10-13 11:03:18 MDT --- "Preference of connecting to only one interface (love to see this one default as described in the bug summary, but would concede the option)" Yes, you've asked for it several times here. The question still remains, WHY? Why would anyone need this? That's exactly what the use cases I'm asking for should describe. "Option to enable / disable each interface." Again, why? For a corner case where you never want to use a certain device (buggy driver, slow card and you got another, faster one, whatever), you can edit /etc/NetworkManager/nm-system-settings.conf. It's an .ini file, add the following section: [keyfile] unmanaged-devices=udi1[;udi2][;...] and NM will never touch that device again. Please, if you ask for a feature, describe why you need it. -- 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=385683 User quentin.jackson@exclamation.co.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=385683#c15 --- Comment #15 from Quentin Jackson 2008-10-14 01:02:23 MDT --- Wow, there has been some goings on here :) a) Sorry, my mistake I meant beta 2 :) b) I don't disagree with what Andrew is saying here as I think they are good options and linux is ALL about options :) I do know however that we are talking about Gnome here and my experience with Gnome seems to be more about taking away options so maybe you're using the wrong desktop Andrew :) In any case a basic rule of bug reports is to have only one report for each bug or similarly related bug so I think for simplicity this bug should really be closed due to the auto selection of fastest network problem now being fixed and a new feature request opened. Once a feature request is opened (which is clearly not a bug) then the powers that be can have a vote on all of Andrews points made above and whether it fits their particular desktop's philosophy. So Andrew would you mind closing this and logging a feature request? Thanks, Q -- 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.