I've got a trick to solve the problem.
Just kill NetworkManager with sudo killall nm-applet, press Alt+F2 and type
nm-applet, now the connection should work!
Tell me if it works even for you
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network
I also have this issue and I am using the iwl4965 driver as well. I can get my
wireless connection to work through Network Manager, but I need to mess around
with it each time I boot the machine. This is definitely not a solution but
hopefully it can help in the diagnostics of the bug. Here
And, my wireless network worked fine with Ubuntu for months before this.
I believe this started happening after installing some updates within
the last 2 months.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice
what you could try is to use gnutls and not nss for the applet/nm-
daemon.
For that change debian/rules as follows:
1. for network-manager: --with-crypto=nss - --with-crypto=gnutls
2. for network-manager-applet: --without-gnutls - --with-gnutls AND --with-nss
- --without-nss
of course as
duped bug 284409 in which author has outlined a workaround. Consider to
test if that works for you too.
Thanks,
- Alexander
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
This has just started working for me. It appears to have been fixed
sometime in the last week.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this
this morning it stopped working for me again, (but vpn started working)
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because
bug 284409 ... is about TLS over wired. Looks similar.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are a member
No, 284409 is also over wireless.
LarryGrover, can you try to add the CA certificate to /etc/ssl/certs and
then rehash it. I.e after putting the CA in for example
/etc/ssl/certs/myUniversityCA.pem, run 'update-ca-certificates --fresh',
and then try again. Without the CA certificate specified in
actually it seems to work for me when i use fluxbox instead of gnome
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you
This started working for me this morning again. Not sure why, nothing
that was updated last night (for me anyway) was drivers, NM,
wpa_supplicant, or kernel.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice
** Attachment added: wpa_supplicant.log.tar.gz
http://launchpadlibrarian.net/18614986/wpa_supplicant.log.tar.gz
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
This is happening for me too with ndsiwrapper and BCM4328. It worked
great yesterday (October 15) and after aptitide dist-upgrade it won't
work at all today. WPA Personal networks work perfectly. I can't
connect using wpa_supplicant alone either.
** Attachment added: Snippet of daemon.log
I got new output from wpa_supplicant after rebooting to use the new wl
driver instead of ndiswrapper. The logging in daemon.log is the same,
and the wpa_supplicant logging is the same after reverting back to
ndiswrapper.
** Attachment added: New wpa_supplicant log
I'm attaching two pieces of wpa_supplicant.log. Both are from
connection attempts using Network manager. The first log file seems to
show two errors:
TLS: Certificate verification failed, error 19 (self signed certificate in
certificate chain) depth 2 for '/DC=edu/DC=marshall/CN=Marshall
** Attachment added: nm-wpa_supplicant-no_CA-cert.log
http://launchpadlibrarian.net/18623813/nm-wpa_supplicant-no_CA-cert.log
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1629
the user there reports it without using NM at all. reopening linux
task, adding wpasupplicant task until we know whats going on.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
Status:
not in progress for NM until we know what causes this.
** Changed in: network-manager (Ubuntu)
Assignee: Alexander Sack (asac) = (unassigned)
Status: In Progress = Triaged
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network
I'm here to give any additional information that might be useful, just
ask.
In my opinion, it looks like something more related to the kernel or
driver rather than NM.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local
On my system this is clearly a Network Manger bug, not a kernel/driver
bug.
I have two kernels installed, 2.6.24-21-generic and 2.6.27-4-generic.
When I boot the older 2.6.24 kernel I cannot connect using Network
Manger, but I connect right away using wpa_supplicant from the command
line. When I
** Attachment added: wpa_supplicant-2.6.24-21-generic.txt
http://launchpadlibrarian.net/18587115/wpa_supplicant-2.6.24-21-generic.txt
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
** Attachment added: nm-2.6.27-4-generic.txt
http://launchpadlibrarian.net/18587119/nm-2.6.27-4-generic.txt
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You
** Attachment added: wpa_supplicant-2.6.27-4-generic.txt
http://launchpadlibrarian.net/18587130/wpa_supplicant-2.6.27-4-generic.txt
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
could you also please attach a tail on /var/log/wpa_supplicant.log?
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you
I would like to tell that the todays update of NetworkManager did not
solve the issue. Same problem, same logs!
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You
This is looking more like an NM issue, however I don't have an AP
capable of WPA Enterprise in order to conclusively prove it.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack (asac)
** Changed in: network-manager (Ubuntu)
Status: New = In Progress
**
I did get connected with Tunnel TLS instead of PEAP, which the NOC group
on my campus told me should not be compatible with there system
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
Reloading the module did not help me at all.
This problem is getting more and more annoying...
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this
Problems with 2.6.27 kernels.
And not only iwl2945, tested with a usb zd1211 chip (3com)
I've tested with 2.6.24-19 and it's working well.
Now I'm testing with 2.6.22-14 and iwl3945 is not working, same behavior
as 2.6.27-6 (today's updates). BUT zd1211 is Working like a charm.
I don't know
It affects at least iwl4965 since this is my case!
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are a member of
I tried reloading the iwl3945 using the disable_hw_scan=1 option:
modprobe -v -r iwl3945
modprobe -v iwl3945 disable_hw_scan=1
This didn't help at all.
Also, I don't think this bug has any specific relation to the Intel
wireless card (iwl3945/iwl4965): I have reproduced the bug using a USB
** Attachment added: syslog when NetworkManager fails using zd1211
http://launchpadlibrarian.net/18342116/syslog-zd1211.txt
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
Also affects prism54 chipsets too.
I have attempted to downgrade several packages to hardy level including
network-manager, network-manager-gnome, dhcdbd, libnm, wpa-supplicant
etc., but all have exhibited the same behaviour of attempting to
connect, and then doing the local disconnect=3 message
Should this generalize to ipw2200 drivers as well?
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are a member of
No change for me loading modprobe -v iwl3945 disable_hw_scan=1.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are
doing the modprobe -v... didn't have any effect either.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are a member
I think this bug was inappropriately changed to iwl3945 + iwl4965. This
is affecting ipw2200 users and I tried it on an atheros card earlier
with similar results.
--
[Intrepid] iwl3945 + iwl4965 -- network-manager will not connect to a WPA
Enterprise network (disassociating by local choice
37 matches
Mail list logo
