I'd sure like to see what you get on the wep router with
network-manager, for thoroughness. I just found out the the b router
that I have that can do wpa is borked and wicd is still not playing nice
with wep. Since this bug is associated with network-manager, let's try
that if possible.
Michael Schultheiss wrote:
> This definitely appears to be a NetworkManager problem rather than a
> problem with the iwl3945 driver. I installed wicd
> (http://wicd.sourceforge.net) and was able to connect to my WPA enabled
> G router without any issues.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd sure like to see what you get on the wep router with
network-manager, for thoroughness. I just found out the the b router
that I have that can do wpa is borked and wicd is still not playing nice
with wep. Since this bug is associated with network-manager, let's try
that if possible.
Michael Schultheiss wrote: wicd.sourceforg e.net) and was able to connect to my WPA enabled enigmail. mozdev. org
> This definitely appears to be a NetworkManager problem rather than a
> problem with the iwl3945 driver. I installed wicd
> (http://
> G router without any issues.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFH7rIDup3 57T5MfTYRApapAJ 4xoqZubXvJmfkbj XWZe1m5YHLTqgCg uGcp elZucqEY=
6AeEvE8DYzkEgBQ
=UzFK
-----END PGP SIGNATURE-----