-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gour wrote:
On Wed, 2006-03-22 at 21:57 +0100, Luka Renko wrote:
I think this is know issue with madwifi drivers: NM does scans also
when conected and madwifi driver cannot perform such scan in
background, therefore it disconnects current
On Wed, 2006-03-22 at 14:50 -0500, Robert Love wrote:
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
I'd like to report that it works for me! Thanks, Robert (and others too,
of course!). The only problem I have that network interface switching
doesn't
Hi!
As I'm receiving more and more requests on KNetworkManager and as the
development is near a 0.1 release, I'd like to know which source code
repository you think public development of KNetworkManager should take
place.
Basically there are two options: I've received an offer to put
On Wed, 22 Mar 2006, Robert Love wrote:
On Wed, 2006-03-22 at 18:38 +, [EMAIL PROTECTED] wrote:
Today I've been trying to connect to a wireless network that uses
802.11x.
I was told by someone who connected using an Apple laptop that I needed
to use TTLS with PAP. In the WPA
On Thu, 2006-03-23 at 07:48 -0500, Dan Williams wrote:
Third option: freedesktop.org SVN (or CVS). Chris Aillon and I were
punting around the idea of putting NM onto freedesktop.org, since it
really is desktop agnostic, a lot like HAL. If there aren't any
objections, I guess that's the
On Thu, 2006-03-23 at 11:48 +0100, Dennis Kaarsemaker wrote:
How about:
_
Key type:| Wep 40 \/ |
|-|
| Wep 64 |
| WPA |
Dennis Kaarsemaker wrote:
...and of course Murphy loves me and decided that somehow madwifi scuks
even harder than I thought - with the neccessary patches applied to NM
and the madwifi Driver all worked fine a few days ago but today it
decided not to do WPA anymore. So I won't be able to test
On Thu, 2006-03-23 at 08:32 -0500, Robert Love wrote:
On Thu, 2006-03-23 at 07:48 -0500, Dan Williams wrote:
Third option: freedesktop.org SVN (or CVS). Chris Aillon and I were
punting around the idea of putting NM onto freedesktop.org, since it
really is desktop agnostic, a lot like
On Thu, 2006-03-23 at 10:04 -0500, Pat Suwalski wrote:
Finally, if you've gotten this far, there is a patch I'm planning to
write that will automatically detect the WEP type, there is no need for
a drop-down box. Hex will be hex, 26 characters/nibbles long. The
password mode for that does
On Wed, 2006-03-22 at 23:29 +0100, [EMAIL PROTECTED] wrote:
NetworkManager right now sets invisible_char to the default value of *
in all .glade files, that is not needed and poses an even bigger problem
if the system default is changed. attached patch removes all
property
On Thu, 2006-03-23 at 10:15 -0500, Pat Suwalski wrote:
Robert Love wrote:
This won't fly.
As just one example, my passphrase at home is a legitimate hex key (I
am, yes, an idiot). Differentiating between ASCII and passphrase is
even harder. We need to ask.
I've seen this in an
On Thu, 2006-03-23 at 10:15 -0500, Pat Suwalski wrote:
Robert Love wrote:
This won't fly.
As just one example, my passphrase at home is a legitimate hex key (I
am, yes, an idiot). Differentiating between ASCII and passphrase is
even harder. We need to ask.
I've seen this in an
On Thu, 2006-03-23 at 10:22 -0500, Dan Williams wrote:
Passphrases can be any length, up to 64 characters. That includes
exactly 26 characters, and since the hex key character space is a subset
of the passphrase character space, there's absolutely no way to
differentiate between the two
On Thu, 2006-03-23 at 02:15 -0600, Steev Klimaszewski wrote:
You could also try
http://madwifi.org/attachment/ticket/462/wext19_060322.patch
I tried the patch and have few issues:
a) the patch is missing WPA2 capabilities and NM reported that my
hardware do not support WPA2.
I added
Robert Love wrote:
Basically:
WEP key: 26 characters, [A-F]|[a-f]|[0-9]
String: 26 characters, no restrictions.
I am saying, my passphrase is a legitimate hex key.
It cannot work beautifully if ASCII and Hex keys are also valid
passphrases.
I don't see how -- to the best
On Thu, 2006-03-23 at 10:43 -0500, Pat Suwalski wrote:
I don't see how -- to the best of my knowledge, the ascii keys are not
allowed to be 26 characters long, and the hex keys must be 26 characters
long...
Right, but passphrases can be either of those things.
Robert Love
Robert Love wrote:
I think many users these days, and most users going forward, use
passphrases, so the best bet we can have is default to passphrase as
the key type and expect our users to change it if needed. Otherwise, as
Dan wrote, we are just asking for confusion.
Hm. Well, then
On Thu, 2006-03-23 at 10:51 -0500, Pat Suwalski wrote:
Hm. Well, then something that would alleviate the annoyance is if the
text box didn't get cleared when the mode is changed. I always end up
pasting in or typing in the key and then selecting the method, only to
lose about 2 minutes of
On Thu, 2006-03-23 at 12:44 -0500, David Zeuthen wrote:
It's very difficult to deal with translations if you're hosted on fd.o
servers. I recommend that you at least keep the applet in GNOME CVS/SVN.
This raises a good point. We need the translators.
Also, Dan, I had another issue I wanted
On 03/22/2006 05:29 PM, [EMAIL PROTECTED] wrote:
NetworkManager right now sets invisible_char to the default value of *
in all .glade files, that is not needed and poses an even bigger problem
if the system default is changed. attached patch removes all
property name=invisible_char*/property
On Thu, 2006-03-23 at 14:01 -0500, Christopher Aillon wrote:
You're right, although I wonder how that snuck in. I made sure that
NetworkManager was not setting the default invisible character when I
was converting Fedora to use a different default Anyway, thanks for
catching it.
On 03/23/2006 02:28 PM, Robert Love wrote:
On Thu, 2006-03-23 at 14:01 -0500, Christopher Aillon wrote:
You're right, although I wonder how that snuck in. I made sure that
NetworkManager was not setting the default invisible character when I
was converting Fedora to use a different
After watching the development of the WPA support in Network Manager I
couldn't wait for FC5. So after I installed I am running into some
issues using NetworkManager.
When trying to connect to an open AP it seems that I get a connection.
The applet shows the signal bars as empty (no signal).
23 matches
Mail list logo
