Re: Usability issues with 0.7 / Ideas for next release.
- From: "Daniel Espinosa" <esodan gmail com>
- To: "Dan Williams" <dcbw redhat com>
- Cc: Patrick <citizen024 gmail com>, networkmanager-list gnome org
- Subject: Re: Usability issues with 0.7 / Ideas for next release.
- Date: Wed, 16 Jul 2008 10:02:17 -0500
2008/7/8 Dan Williams <dcbw redhat com
On Tue, 2008-07-08 at 14:45 +0200, Patrick wrote:Right, BT support will come post-0.7. First for DUN, then for PAN.
> While the improved 3G and vpn capabilities are nice there are a few
> small issues that could be addressed to improve the next version
> 1. Would be nice if NM with the right packages installed could handle
> pand connections to simplify connecting to the internet via bluetooth
You can certainly bring up the wired interface, but the default route
> 2. If one has a wired connection then its really hard to switch to a
> wireless one without unplugging the cat5 or usb connection. It'd be
> better if it was as easy as point n click.
will stay on the wired device because it's plugged in. I'm not sure I
see a good use-case here... you'd be connected to wireless after picking
it from the menu, so you'd be able to access anything on that network
In some cases you can have a wired office connection to corporate network and a wireless connection to a public network may you want to use (may you have a movil internet connection), then is useful to switch between interfaces.
This is also a common request. As another data point, Mac OS X requires
> 3. Having the user choose what type on encryption the network uses when
> entering the password isn't of much use, most users don't know the
> first thing about encryption, it could be automatic. (works in win:()
you to choose WEP key types just like NM does. Most vendor tools from
D-Link, Linksys, etc that don't use WZC also make you choose.
The right solution is to try successive key permutations quickly, but we
can't do that easily. First, drivers suck. Second, the kernel API for
wireless isn't conducive to this and doesn't give enough feeback to make
it work. Third, with WEP you simply don't know whether the key is right
or not until a DHCP attempt has timed out, which can take 45 seconds.
So taking up to 2 minutes to connect to a network just sucks.
The fundamental problem is that both WEP ASCII and Hex key types overlap
with the WEP passphrase type. Most places use passphrases. But I've
personally seen places that use a what _looks_ like a hex key as a WEP
Why don't select the most common one; may be this could be a setting may for different contries and distribution selection.
Taking 45 seconds to connect automatically to the most common encription is great; and if it fails then ask for encription type.
Trabajar, la mejor arma para tu superación
"de grano en grano, se hace la arena" (R) (en trámite, pero para los cuates: LIBRE)
] [Thread Prev