[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2008-08-24 Thread tl
_THIS_ particular issue reported in _this_ bug thread was observed under
Fiesty and rectified in Gutsy.

There is a different and current wireless issue with WPA in Hardy
reported in the following bug report:

https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/207446

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2008-08-23 Thread Rolando F. Blanco C:.
Hi everyone,

Well, I'm testing Intrepid in my wife Laptop, this one is an IBM
ThinkPad T40, and have a Wirelless AIRONET 802.11 from CISCO, well, this
one don't want to connect to any kind on network that have any kind of
encription. I did try WEP, WPA and WPA2 wirelless networks, and was not
possible to connect.

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-10-07 Thread Alexander Sack
network manager has come a long way since feisty. I assume this issue is
fixed not in gutsy. Please reopen if you still see _this_ particular
issue in latest gutsy network-manager (0.6.5-0ubuntu15).

Thanks,
 - Alexander

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Medium
   Status: New = Fix Released

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-05-06 Thread BenzSL600
I´m very new to Ubuntu, I tried following the instructions above, but still 
can´t get My Netgear WG511 v1 network card to connect to my router using WPA. I 
think I am having trouble creating the *.wpa.config file. 
[EMAIL PROTECTED]:~$ network={
[EMAIL PROTECTED]:~$ ssid=¨PGMNT¨
[EMAIL PROTECTED]:~$ #psk=¨¨
[EMAIL PROTECTED]:~$ psk=
[EMAIL PROTECTED]:~$ }
bash: syntax error near unexpected token `}'

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-05-06 Thread tl
See my solution at:

http://ubuntuforums.org/showpost.php?p=2585938postcount=19

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-05-03 Thread tl
Problem with Network Manager in Fiesty - I think NM is unable to handle
and use keys with the keyring modules based on my observations.

Problem with the native Prism54 drivers in Fiesty - confirmed, see bug #
90902

I was finally able to get NDISwrapper working with the Windows driver
(netwg511.inf) again--as before with Edgy--and use WICD in place of
Network Manager--completely removed now.  Wireless connection to my
802.11g network with WPA is working again.  Still have just one issue
with this configuration, when the IP lease expires, the Internet and LAN
connections die and I would have to manually reconnect via WICD.

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-05-02 Thread Golden Tiger
My network card blinking its' head off is a bit strange... but at least
the instructions in this bug report allow my wireless card to connect to
my WPA network.  Isn't the network manager supposed to use
wpa_supplicant if necessary to achieve a connection?

Here, I'm using Wifi Radar to kinda work through the management of my
wireless card, but it isn't an optimal solution.  I'm not certain who to
blame here though, the wireless card drivers or the network manager
giving up,

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-04-29 Thread tl
I think there may be other issues with the native prism54 drivers
besides the WPA problem with Network Manager.  After some more extended
uses and rudimentary testing, I noticed that the wireless connection's
performance is severely degraded.  The data throughput rate is about a
quarter of what its maximum capability used to be under Edgy, and it
fluctuates wildly.  It now takes about 4 times longer than before with
Edgy to transfer a ~1GB file between two PCs on the LAN.  I also noticed
that the network activities LED (amber) on the WG511v1 flashes
constantly even when the wireless connection should be at idle.
Normally, this LED stays dark-not flashing dimly and rapidly--and
doesn't light until there's traffic activities.  I suspect that the
drivers may be issuing extraneous packets and tying up the bandwidth for
actual data transfers.  I'm no network expert so I'm unable to sniff and
check for those suspected packets.  I'm uncertain but I also believe
that the wireless connection and bit transfer rate is unaffected and is
operating at its 802.11g peak rate of 54Mbps--even with all the detected
network signal levels being degraded too.  Again, I think there may be
other issues with the native drivers too...

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-04-28 Thread tl
I too have encountered the very same issues, symptoms and results as
those already reported in the previous posts.  Working Edgy wireless
setup with WG511v1, WPA using Network Manager without wpa_supplicant,
ndiswrapper  netwg511.inf.  Upgraded to Fiesty, and wireless no longer
works.  Removed ndiswrapper and Network Manager, enabled and configured
wpa_supplicant, and wireless connection is now working.  However, using
WICD in place of Network Manager, the signal levels of all detected
networks seem to be significantly lower than what were observed with
Edgy.  Hopefully, the Network Manager can be fixed soon... this is only
a temporary solution.

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-04-28 Thread Peter Enzerink
I have a very similar issue with a WG511v1 except I have:

wiphy0: hwaddr 00:09:5b:45:57:41, isl3890

rather than

wiphy1: hwaddr 00:0f:b5:1d:67:7f, isl3886

I haven't tried a manual setup as I use WEP rather than WPA (separate
airo card doesn't support WPA).

See also https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/105357

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-04-23 Thread gergnz
I am also having this same issue, and wpa_supplicant is working.

Network_manager just gives up.

dmesg (loading module)

[  146.937273] p54: LM86 firmware
[  147.916780] wmaster0: Selected rate control algorithm 'simple'
[  148.099899] wiphy0: hwaddr 00:09:5b:92:b9:62, isl3890
[  148.639451] wmaster0: Does not support passive scan, disabled
[  148.662593] eth1: starting scan
[  149.321098] eth1: scan completed

Running wpa_supplicant

[EMAIL PROTECTED]:~# wpa_supplicant -Dwext -i eth1 -c test.wpc.conf -K
ioctl[SIOCSIWMODE]: Device or resource busy
Could not configure driver to use managed mode
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - Trying to associate with 00:13:10:07:ff:59 
(SSID='MYAP' freq=2437 MHz)
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - ioctl[SIOCSIWMODE]: Device or resource busy
Association request to the driver failed
Associated with 00:13:10:07:ff:59
WPA: Key negotiation completed with 00:13:10:07:ff:59 [PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:13:10:07:ff:59 completed (auth) [id=0 
id_str=]

Running dhclient.

[EMAIL PROTECTED]:~# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/eth1/00:09:5b:92:b9:62
Sending on   LPF/eth1/00:09:5b:92:b9:62
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 10.250.250.3
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 10.250.250.3
bound to 10.250.250.221 -- renewal in 40886 seconds.

excert from /var/log/syslog for networkmanager.

Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
wpa_driver_wext_set_drop_unencrypted
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
State: SCANNING - ASSOCIATING
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
wpa_driver_wext_set_operstate: operstate 0-0 (DORMANT)
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
WEXT: Operstate: linkmode=-1, operstate=5
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
wpa_driver_wext_associate
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
Association request to the driver failed
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
CTRL_IFACE monitor send - hexdump(len=40): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 
77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 34 38 35 34 2d 
35 00
Apr 23 21:08:57 manuel NetworkManager: information^Iwpa_supplicant(5854): 
Setting authentication timeout: 5 sec 0 usec
Apr 23 21:08:57 manuel kernel: [  205.118740] eth1: starting scan
Apr 23 21:08:58 manuel kernel: [  205.775850] eth1: scan completed
Apr 23 21:09:02 manuel NetworkManager: information^IActivation 
(eth1/wireless): association took too long (60s), failing activation.
Apr 23 21:09:02 manuel NetworkManager: information^IActivation (eth1) failure 
scheduled...
Apr 23 21:09:02 manuel NetworkManager: information^IActivation (eth1) failed 
for access point (MYAP)
Apr 23 21:09:02 manuel NetworkManager: information^IActivation (eth1) failed.
Apr 23 21:09:02 manuel NetworkManager: information^IDeactivating device eth1.
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): L: 
External notification - EAP success=0
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
EAPOL: External notification - EAP fail=0
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
EAPOL: External notification - portControl=Auto
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
Wireless event: cmd=0x8b1a len=24
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
Wireless event: cmd=0x8b19 len=8
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
Received 349 bytes of scan results (2 BSSes)
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(5854): 
Scan results: 2
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(-1): 
CTRL-EVENT-TERMINATING - signal 15 received
Apr 23 21:09:02 manuel NetworkManager: information^Iwpa_supplicant(-1): 
CTRL_IFACE monitor send - hexdump(len=40): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 
77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 34 38 35 34 2d 
35 00
Apr 23 21:09:02 manuel NetworkManager: 

[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-04-22 Thread Karel Demeyer
I second this on my freshly installed feisty system;

Hardware:
02:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism 
Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)

Kernel:
Linux kryptonix 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 
GNU/Linux

Modules loaded:
prism54pci 13440  0 
prism54common  12288  1 prism54pci
mac80211  175364  3 rc80211_simple,prism54pci,prism54common
cfg80211   22920  1 mac80211

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 105858] Re: WPA not available from Network Manager, but works from cmdline wpa_supplicant

2007-04-12 Thread JohnCollaros
PS - Starnet.wpa.conf was generated using wpa_passphrase
and looks something like the following:


network={
ssid=StarNet
#psk=
psk=XXX
}

-- 
WPA not available from Network Manager, but works from cmdline wpa_supplicant
https://bugs.launchpad.net/bugs/105858
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs