Bug 186315

Description of problem:
Wireless should not fall back to wired connection with applications which are
currently unable to detect (or cope with, in many cases!) network changes. 

Currently, if one has a functional wired connection, disconnect it and fall to
last known good wireless, and then reconnect the wired connection, it falls back
to the wired one.

When it's true that various apps (gaim, vpn, ssh, evolution, among others)
correctly detect a loss of network/network change, I agree that wired should
always be defaulted to if available, for security of connection reasons. 

But as is, we need to be consistent in our behavior, and we do not currently
fall to wired if a wireless connection was specifically selected and wired is
plugged in.

Version-Release number of selected component (if applicable):
NetworkManager-0.6.0-3

How reproducible:
Always

Steps to Reproduce:
1. Connect a wired connection on a machine/user combination which has already
had a functional and accessable wireless connection set up.
2. Disconnect the wired connection, and watch it fall back to the wireless
connection.
3. Reconnect the wired connection.
  
Actual results:
Falls back to wired.

Expected results:
Should not fall back to wired (at least with things as they currently are).

Additional info:
The best thing to do would be to fix the confused behavior of the various apps
which have trouble detecting and/or handling the loss of or change of network
connection, and have it always fall to a wired one. This is not an option right
now, though.

When it comes time to be able to have multiple connections at the same time, via
NM, that'll be an entirely different question (and my suggestion would be that
multiple functional network connections needs to be an advanced setting, and not
the default one).