Anyone still getting disassociating by local choice (reason=3) should
also read bug #548992 and consider trying
iwconfig wlan0 power off
to disable power management.
** Changed in: network-manager (Ubuntu)
Status: Triaged = Fix Released
** Changed in: wpasupplicant (Ubuntu)
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: knetworkmanager
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: linux (Ubuntu
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in:
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: network-manager
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: wpasupplicant
I realized I had made a mistake, Intrepid Ibex 8.10 will reach EOL on
30 APRIL 2010.
Sorry for this.
Anyway, I think that one month doesn't make any difference now.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local
This bug is not about issues with OpenVPN.
** Changed in: network-manager-openvpn (Ubuntu)
Status: Triaged = Invalid
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
** Branch linked: lp:ubuntu/network-manager-applet
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(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 face this problem after upgrading to Karmic today. ATM I've no idea if it's
kernel or network-manager caused, but my wifi-commection is flapping constantly
and the only error I see is: disassociating by local choice (reason=3)
btw: I'm using a BCM4318 with the b43 driver.
--
[Intrepid]
** Changed in: knetworkmanager (Debian)
Status: Unknown = New
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification
Can anyone reproduce this using the latest Karmic? Network Manager in
Karmic is substantially improved from Jaunty and earlier.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
Indeed, my severe problems with connecting to WPA2-PEAP (MSChapV2) went
completely away with the newer Karmic versions. (Intel 5300 WiFi card
here, 32bit OS.)
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice
I can't test anymore. I am no longer working at the company that had
it.
On Mon, Oct 5, 2009 at 3:29 PM, hasi why...@nurfuerspam.de wrote:
Indeed, my severe problems with connecting to WPA2-PEAP (MSChapV2) went
completely away with the newer Karmic versions. (Intel 5300 WiFi card
here, 32bit
** Changed in: dell-mini
Status: New = Confirmed
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are a
At the moment, on Jaunty 32-bit, all repo's enabled, I can connect on
every place at my university. However, after 15 minutes or so, the
connection is dropped and I have to manually select the wireless network
again.
Using wpa_supplicant, everything works fine.
--
[Intrepid] iwl3945 + iwlagn --
** Also affects: dell-mini
Importance: Undecided
Status: New
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification
If I reboot (sometimes a few times) or log out (also a few times) it
will reconnect on my Updated Beta jaunty on my asus 1000HE.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
What is the status on this bug? I was suffering from this problem on
Intrepid for quite long time, but now using the kernel
2.6.27-11-generic and the iwl3495 from compat wireless
(http://linuxwireless.org/en/users/Download) dated of 2009-03-31 I do
not have any problem.
I am now connected in my
Having updated to Janty Beta this morning, things appear much improved.
The connection disconnects but reconnects itself without intervention.
Running NetworkManager with --no-daemon I see the following errors
listed, not sure if these relate to all the disconnects but are probably
at least some
Danny, have you tried my suggestion to run in a terminal iwconfig wlan0
essid ssid_name? (substitute for wlan0 and ssid_name as appropriate). I
have no idea why this works, but I have had a 100% connection success
rate over the last 6 weeks. I find it works either a) to issue the
command once NM
Danny, you might also want to check out bug #347572: iwl3945 unable to
connect to WPA personal without linux-backports-modules being installed
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
I'm in aup-to-date Jaunty Alpha 6 and i'm experiencing this on multiple
machines (32-bit and 64-bit), across multiple networks WPA and WPA 2
personal.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3)
hey, had the same issue that chris walkelin describes at comment #79 (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272185/comments/79 ) while
connection to the wireless network at my university (also using eduroam)
i'm not using ubuntu, but it seems that is the same error.
using
Thanks for the suggestion, but I'm pretty sure what I'm seeing is this
bug in Network Manager:
http://bugzilla.gnome.org/show_bug.cgi?id=565065
Uri
On Mon, Mar 2, 2009 at 4:34 AM, LHM 06101...@gmx.at wrote:
hey, had the same issue that chris walkelin describes at comment #79 (see
I seem to be able to connect if, using the CLI, I issue the command
iwconfig wlan0 essid northwestern. Is it apparent to anyone why this
command would help NM connect?
I'm not sure the sequence matters, but if NM fails to connect automatically, (I
keep getting the certificate dialog), I click
Hey so first thing, I also tried installing the packages from the Jaunty
repo that were suggested but that didn't help at all. Mine is a WPA PEAP
wireless lan. I can connect instantly with wpa_supplicant but not with
network manager.
my wpa_supplicant.conf looks like this (I've tried to remove
Here's a successful connection
** Attachment added: connect_success.out
http://launchpadlibrarian.net/21806265/connect_success.out
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
Yes, I tried installing the jaunty packages. After updating my
repositories, updating and selecting the packages, Synaptic forced me to
install some other (dependent) packages. However, it did not solve my
problems with WPA2/TTLS/PAP; I still had trouble connecting and took a
lot of tries before
** Bug watch added: Debian Bug tracker #461932
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461932
** Also affects: knetworkmanager (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461932
Importance: Unknown
Status: Unknown
--
[Intrepid] iwl3945 + iwlagn --
Ernst -- did you try my fix?
Dan
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(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 Kubuntu
Bugs,
I think I'm also affected by this bug.
I'm running Ubuntu 8.10 with all repositories enabled (means I run kernel
2.6.27-11-generic (uname -r)).
lspci |grep 3945
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan]
Network Connection (rev 02)
At home, I can connect to my
Dan asked earlier for a log of a successful connection. Here are both
(these are using the default driver, which I believe is iwlagn).
Successful connections remain sporadic.
Successful:
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:11:92:3e:79:80 (SSID='Northwestern' freq=2447 MHz)
Unfortunately changing the driver isn't the answer. And despite my initial
flurry of success, wpa_supplicant on the command line isn't the answer
either. It may connect with a slightly higher probability, but most of the
time I don't connect however I try.
On Tue, Jan 13, 2009 at 10:31 PM, Dan
Network-manager still does not connect. With a connection set up as
described above (wpa2, peapv0, mschapv2) I still get the dialog box
asking if I want to select a certificate, followed by no connection. The
log (/var/log/wpa_supplicant.log) contains an endless string of the
following:
NM version is 0.7~~svn20081018t105859-0ubuntu2
Good point about the driver. If I try to specify iwlagn wpa_supplicant
doesn't know what that is.
One more weird thing to mention. I can use wpa_supplicant manually to
connect right after rebooting. If I bring down wlan0 and then try to
reconnect,
It could still be a driver issue -- as you manually specified the wext
driver in that command...
Out of curiosity, what version of network manager are you running? Maybe
the jaunty sources got updated (and re-broken)? Get the exact version #
from synaptic (should be kinda weird with some ~~
Try running wpa_supplicant again without the -D setting eg:
sudo wpa_supplicant -c wpa_supplicant_nu.conf -d -iwlan0 -B
Can you get the versions of all the packages in my initial post?
Thanks
Dan
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise)
Based on two tries -Dwext seems to be necessary.
Here are the versions from aptitude show:
wpasupplicant 0.6.6-2
libnm-glib0 0.7~~svn20081018t105859-0ubuntu2
libnm-util0 0.7~~svn20081018t105859-0ubuntu2
libxcb-render-util0 0.2.1+git1-1
Those packages are ok I'm officially out of ideas ... :-/
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you
On Tue, Jan 13, 2009 at 7:29 PM, Dan Bracey cpuda...@gmail.com wrote:
Those packages are ok I'm officially out of ideas ... :-/
Is there a way to tell network-manager to use a different wireless driver?
(Since wext seems to work, at least some of the time.)
--
[Intrepid] iwl3945 +
Sure, I didnt think that about that... Try adding this line to
/etc/network/interfaces:
wpa-driver wext
You need to be root to edit that file. Ex. gksudo gedit
/etc/network/interfaces. You'll probably need to reboot after editing
the file.
Dan
--
[Intrepid] iwl3945 + iwlagn -- network-manager
Unfortunately Dan's fix (using the Jaunty networking packages in
Intrepid) does not work for me. My laptop is a Lenovo X200s with a 5100
AGN adapter, using iwlagn. My university network uses WPA2, PEAP (ver
0), MS-CHAP2. I have always had erratic connections using Intrepid ---
sometimes the laptop
As far as KDE goes, I couldn't get that to work right using the latest
KUbuntu. There were some knetworking packages that I could have updated,
but those depended on a lot of other packages. I didn't want to get
Jaunty stuff and Intrepid stuff too intertwined, so I left it alone...
It's
Oh I forgot to mention -- if you are required to provide a certificate,
it must be an *.pem file in /etc/ssl/certs. Make sure you update your
certificate cache (see directions earlier in this thread.)
Dan
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
Following posted directions for Windows
(http://www.it.northwestern.edu/oncampus/wireless/wireless-connections
/wireless-win.html), wireless is 802.1x/WPA2, PEAP, MSCHAPv2. I figured
out PEAPv0 while getting wpa_supplicant to work under Puppy Linux (it
worked flawlessly, but on a different laptop,
It would help if you attached your /var/log/wpa_supplicant.log file to
this bug report. Try and get connected a few times and then also see if
you can get a few failures in there. If you have intermittent
connections -- it really sounds like a driver thing (or a thing on
northwestern's end.)
From
I used the workaround hinted by Dan Bracey. It worked perfectly on a
Dell E6400 with Intel 5300 WiFi. I fixed my previous problems connecting
to a WPA2 Enterprise access point using PEAP/MSCHAPv2.
I am running kubuntu, however, I was using nm-applet instead of
knetworkmanager to connect to the
Glad to hear it worked for you hasi. I can test the stuff again with
KUbuntu on Monday. I'll report back.
Dan
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
This simple workaround has been helping with wpa enterprise with tkip
that worked in hardy but not in Intrepid.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263963/comments/89
Using gconf-editor to remove the ccmp entries worked for me too. :)
First off - this bug is *not* invalid. Don't know why it is marked as
such. At any rate I think I've got a simple solution. It's off the wall,
but it works on a variety of chipsets (atheros, ipw2200...).
## WARNING: Following these instructions may break your Intrepid
installation. They worked
Hello, I'm having an issue that (should) be the same.
When I try to connect to a WPA network the wpa_supplicant.log is:
CTRL-EVENT-SCAN-RESULTS
No network configuration found for the current AP
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event -
** Changed in: knetworkmanager (Ubuntu)
Status: New = Invalid
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification
** Also affects: knetworkmanager (Ubuntu)
Importance: Undecided
Status: New
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug
Niall Murphy wrote:
I believe i am suffering from the same bug.
I connect fine to my office WiFi but i loose the connection after 5 or 10
minutes and must reconnect again.
This problem started when i upgraded to Intrepid from Hardy.
Is that a A, G or N network where you loose your
Omer wrote:
Ok guyz... this seems like one of those long hauls. In the meantime, I
was thinking about rolling back some of the packages to Hardy. NM is
probably not it, since i get the problem with command line WPA
supplicant as well. Any suggestions? Or should I start the hit and trial
This bug was found in the Intrepid development cycle; removing
regression-potential and marking as regression-release.
** Tags added: regression-release
** Tags removed: regression-potential
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network
Ok guyz... this seems like one of those long hauls. In the meantime, I
was thinking about rolling back some of the packages to Hardy. NM is
probably not it, since i get the problem with command line WPA
supplicant as well. Any suggestions? Or should I start the hit and trial
method?
Apologies for
hello,
I am guessing this isn't resolved yet. My experience is as follows.
Hardware = Gateway M280, intel pro 2200
Connecting to Eduroam = WPA-EAP, TKIP, PEAP, MSCHAPV2 (Uni of York)
NM just doesn't work. I have been attempting off and on for the past
month now and it hasn't connected once. I
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
Kartoch
I tried your eduroam scripts and configs[1] and with only a couple of
tweaks it works great.
I had to drop the -Dwext from the wpa_supplicant line in the script.
I also had to change the pap setting to PEAP from TTLS.
Thanks
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the -u parameter) but
Please stop adding random me too; this and that or whatever comments to
the bug report... it's an order of magnitude too large anyways already,
and I have seen few comments add new information. They are more or less
just IRRELEVANT(!) variants of comments already here.
--
Matthias Andree
--
Still not working for me ... WPA/WPA 2 Personal, not Enterprise.
Intrepid, uniquely, does not work. The logs are filled with the
following:
Dec 10 10:30:58 noel-intrepid kernel: [ 1277.187007] wlan0: authenticate with
AP 00:15:c7:82:02:70
Dec 10 10:30:58 noel-intrepid kernel: [ 1277.190341]
I think that the following command:
sudo kill -SIGUSR1 `pidof wpa_supplicant`
Should turn on debugging until you restart.
To make it permenant then you need to change the line in the file
/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service
from:
Note for the above:
This is going save a lot of possibly secret info into
/var/log/wpa_supplicant.log so after you have finished debugging you
probably want to remove that file and also think twice before just
posting it online if you value the info in it.
--
[Intrepid] iwl3945 + iwlagn --
Niall, what do you mean by worse?
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(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 Ubuntu
Bugs,
By worse I mean that Network Manager looses the connection more
frequently.
Seems to happen most when i use the network intermittently, for example, using
IM software, or when browsing the web.
I lost connection 2 times while composing this message.
when the computer is left idle it seems to
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy [EMAIL PROTECTED] wrote:
By
Using the recent updates from intrepid-proposed the problem seems to be
getting even worse.
The packages are
network-manager-gnome version 0.7~~svn20081020t000444-0ubuntu1.8.10.1
network-manager version 0.7~~svn20081018t105859-0ubuntu1.8.10.1
It is an Eduroam network
http://www.eduroam.org/
the timeout tuning fix that seems to fix a few cases is now targetted
against bug 292054 ... for which the SRU will happen now.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
How can i change my PEAP version from 1 to 0.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(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
You change in on the Wireless Security tab for the network you are
trying to connect to. It's a drop down called PEAP Version and the
options are Version 0 or Version 1.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by
It may be a dbus problem because wpa_supplicant -u fails to connect to
dbus, and if it is automatically launched by network-manager, wpa_cli or
wpa_gui cannot connect to the supplicant.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network
I'm using network-manager version 0.7~~svn200810, and I was able to
successfully connect to a WPA 2 network today that I could not before.
I'll keep my eye on it, but it appears that this problem has been
resolved for me.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a
One additional note, I did change my PEAP version from 1 to 0. Not sure
if that's what fixed it, but it's worth trying if you are having
trouble connecting to WPA2 networks.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
Trouble-a-cat limited
--
[Intrepid] iwl3945 + iwlagn -- network-manager
Hi,
I had installed Kubuntu 8.10 and was not able to connect to our wireless
router which has WPA2-PSK security configuration.
My computer was disconnecting by printing the following debug message:
wlan0: disassociating from by local choice (reason=3)
After installing package
(i386):
This was affecting me but after updating to the networkmanager as posted
by Alexander it appears resolved. I run a Lenovo T61 with an Atheros
AR5212 (IBM device 058a) and my association was timing out to an AP with
WPA-Personal ( PSK ) enabled. Thanks Alexander !!!
--
[Intrepid] iwl3945 + iwlagn
Is there any progress on the Enterprise aspects of this bug? It seems
that NM is trying too hard and specifying more parameters than are
required in most cases by wpa_supplicant. Some method of not specifying
the phase2 authentication options would be very interesting to see as,
at least in my
Same here, using intel ipw2915, on hardy it worked perfectly.
Network manager refuses to connect to WPA Enterprise with TKIP and PEAP.
Using a script to deactivate network manager and connect directly via
wpa_suplicant works fine.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not
Updated snap-shot worked great for me! Just need to use PEAP v 0
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because
I have this problem also on my university campus, WPA EAP, we use PEAP
and MSCHAPv2 there. It worked fine under hardy, but now under intrepid
it works only sometimes... I have to reconnect again and again, till it
works, sometimes five minutes, sometimes twenty minutes...
And I use the new iwlagn
Been informed that using WPA PEAP, try connecting using PEAP v0 instead
of v1 - it makes it magically work in some cases [notably, on JHU's
Hopkins wireless network].
Odd, but effective.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network
** Changed in: wpasupplicant (Ubuntu)
Assignee: Reinhard Tartler (siretart) = (unassigned)
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received
I tried with wpa supplicant, and was unsuccessful:
network={
ssid=dedasys
key_mgmt=WPA-PSK
proto=WPA
psk=not my real super secret phrase
}
Here are the results with -d enabled:
[EMAIL PROTECTED]:~# wpa_supplicant -d -c ./wpa_supplicant.conf -ieth1
Initializing interface
Workaround: KNetworkManager has an expert settings option in the profile
editor. If you play with that, I've seen some success in getting things
to connect.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice
WPA Personal worked fine for me in Hardy, and has ceased to work with
the Intrepid upgrade. I tried the PPA repository posted above, but that
doesn't make things better.
Kernel: Linux fortrock 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC
2008 i686 GNU/Linux
Wifi chipset: 0b:00.0 Network
I tried this. Setting IP config manually, but it didn't worked.
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you
I believe i am suffering from the same bug.
I connect fine to my office WiFi but i loose the connection after 5 or 10
minutes and must reconnect again.
This problem started when i upgraded to Intrepid from Hardy.
It is an Eduroam network
http://www.eduroam.org/
WPA/WPA2, EAP-TTLS, PAP
using
Same here with 2.6.27-7 and iwl3945. I get this error when trying to
connect to my wpa-psk or to a completely open wireless network.
But: As soon as i deactivate dhcp and set a static ip gateway,
everything works fine. connection is up. (both the wpa psk and the open
one)
--
[Intrepid] iwl3945
I get the disconnecting by local choice (reason=3) message but on WPA-
PSK on a FON router, as other have reported. Very occasionally it will
connect but most of the time asks me to re-enter a password.
I have tried using kernel 2.4.24 from hardy as this had the iwl4965
driver, but the results
I can confirm that in my case at least the following wpa_supplicant conf
file works as expected without chnaging anything else other than
stopping NetworkManager from running.
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=essid
proto=WPA2
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
** Attachment added: Output of a succesfull wpa supplicant connection attempt
http://launchpadlibrarian.net/19376404/wpa_supplicant.log
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
Please check out my comment
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/292054/comments/7
to see if everyone else agrees with it.
Thanks
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice
I compared my working wpa_supplicant file with the config that
networkmanager generates (according to the log) like suggested in
comment 101. There are a lot of differences, but I was able to pinpoint
on the phase2 property. My working wpa_supplicant file looks like this
(password changed):
** Attachment added: wpa_supplicant command-line success with debug
http://launchpadlibrarian.net/19385750/wpa_supplicant_cli.log
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
be careful, you have _two_ phase2 keys in your conf now ;)
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
https://bugs.launchpad.net/bugs/272185
You received this bug notification because you are
Ouch indeed... I guess I was a bit to enthusiastic.
Anyways, leaving out the first phase2 key, and thus only keeping the one
from networkmanager, doesn't work either.
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=NEWTEC_CORP
mode=managed
proto=WPA
key_mgmt=WPA-EAP
** Attachment added: daemon.log for NetworkManager failed connect
http://launchpadlibrarian.net/19385668/daemon.log
--
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
1 - 100 of 143 matches
Mail list logo
