Changing the password on my FON AP *half-solved* the problem : one of my
computer has been able to connect to the WPA-protected network (with a
RT8187 chip), but no the other one (with an intel 3945ABG chip).
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You
asac nm4
** Attachment added: syslog
http://launchpadlibrarian.net/19096751/syslog
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: wpa_supplicant.log
http://launchpadlibrarian.net/19096757/wpa_supplicant.log
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Trying to associate with 00:15:70:4d:bc:18 (SSID='CAMPUS-AIR' freq=2412 MHz)
CTRL-EVENT-SCAN-RESULTS
Associated with 00:15:70:4d:bc:18
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
EAP-PEAP: Failed to select forced PEAP version 1
Oops, forgot to type that I am connecting to a WPA2 network, using
PEAP... It doesn't connect, just asks me for the username/password over
and over.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Same here, from 8.10 final LiveCD. My system is a HP 8510p, while the router is
an Asus WL-520g.
Ubuntu 8.04.1 works just fine.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Didn't work with updates. Didn't work with turning off avahi-daemon.
Anything below has indentifiable info replaced with [ and ] .
I tried to use the following script instead of nm-applet/networkmanager
to see if its isolated to networkmanager:
---
#!/bin/bash
sudo wpa_supplicant -iwlan1
I killed NM and then started it from cli.
It still failed to accept PW.
$ sudo pkill nm-applet
$ sudo nm-applet
(nm-applet:10429): atk-bridge-WARNING **: AT_SPI_REGISTRY was not
started at session startup.
(nm-applet:10429): atk-bridge-WARNING **: IOR not set.
(nm-applet:10429):
I'm back. I have a guess as to why my solution worked for me and not
for mistryous... I hadn't tried to connect to a WPA Enterprise
network... It DOESNT WORK. Although my wpa2personal now works fine I
am unable to authenticate on my school's WPAenterprise (PEAP - TKIP -
MSCHAPv2). It worked fine
WPA2 back online here with linux-firmware_1.2
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
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
That is an interesting note from Stéphane. For summary, I have PEAP -
CCMP - MSCHAPv2.
Is it in OpenSSL or in the EAP-TLV container format from my log above?
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member
When I run wpa_supplicant it doesn't get nearly that far into doing
things so I've never seen it show EAP-TLV nor anything else. According
to Microsoft's Tech Specs on PEAP-MSCHAPv2 the EAP-TLV is just a part of
the connection process or something? http://technet.microsoft.com/en-
I got it working.
I changed the WPA-key in my router.
After that everything worked fine.
I have no clue why it did not work with the old one. I more than triple checked
it.
Also it did not work with an upgraded 8.04 machine where the WPA-key must have
been correct.
Anyway, try setting a new
Intrepid keep asking for WPA2 passpharse, when connecting to my Fon+ router,
running firmware 1.1.2 r1
I figured that if I stop the avahi-daemon, things work properly!
The avahi-daemon seems to fire packets before DHCP address is obtained,
which confuses certain routers.
So, give it a try if
Stopping avahi-daemon doesn't solve the issue for me.
Connecting to a FRITZ!Box Fon WLAN 7170 (mode 'WPA+WPA2') keeps asking
for authentication and does not result in a connection.
From same machine connecting to a Linksys WRT54GC (WPA2 Mixed mode)
makes a connection that is working for a little
Stopping avahi-daemon doesn't solve the issue for me either. I can
confirm that this issue is very much in the kernel though, because I'm
currently on wpa2 wireless from Intrepid but with 2.6.24-21.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug
Just tried it, but kernel 2.6.24-21 doesn't solve it for me.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have no idea what fixed the problem. I justinstalled a fresh copy of
Intrepid RC. Then I ran all of the updates over ethernet. Then I enabled
my wireless restricted drivers. Now wpa2 works fine even with 2.6.27...
So I have no idea why it now works but at least it does for me.
--
wpa intrepid
I tried again with the release candidate of Intrepid, and still no WPA2.
It throws away my password and fills the password box with a lot more
characters than were ever in my password to begin with when the re-enter
the password dialog appears. Fixing the password in the box doesn't help
anything.
Michael Stempin wrote on 2008-10-22:
Same bug here with WPA.
Unencrypted connects just fine.
This is on a Dell XPS m1330 with Intel 4965.
---
Confirmed here with the same laptop model (Dell m1330), syslog looks
similar so won't attach another until further info is requested.
Linux is
Same bug here with WPA.
Unencrypted connects just fine.
This is on a Dell XPS m1330 with Intel 4965.
syslog attached.
** Attachment added: syslog
http://launchpadlibrarian.net/18795601/syslog
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug
Adding my syslog for my intrepid with my Ralink 2860 chipset.
** Attachment added: Syslog
http://launchpadlibrarian.net/18799407/syslog.log
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs,
I looked over logs for my username in our Radius server and found that
my username or password was incorrect. I tried to log in to the setup
from another computer, and it worked fine. I changed my password just
in case from another computer.
I then tried to login again from my computer with the
** Attachment added: syslog-wep
http://launchpadlibrarian.net/18689215/syslog-wep
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I have the same symptoms.
Network-Manager keeps asking for a password when trying to comnect to a
WPA-encrypted SSID.
However, I found out it works when switching off encryption in my router
or even using WEP.
syslog when trying to use WPA and working WEP connection attached.
cat
Having the same bug on my fresh install of intrepid with a WPA AP.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have a similar issue. Using the same access point as under Hardy,
Intrepid fails to authenticate to WPA2. I've tried using hidden and non-
hidden ssid. I've also tried from both networkmanager and from wicd.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You
How is it that an older kernel can be the solution?
$ uname -a
Linux blubug 2.6.27-6-generic #1 SMP Tue Oct 7 04:15:23 UTC 2008 x86_64
GNU/Linux
I have this kernel, and newer users on have other older kernel.
Currently I can connect to some wifi networks but it takes me several
tries (all
Users confirm that reverting to an older kernel fixes it.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
** Changed in: linux (Ubuntu)
Importance: Undecided = High
Status: New = Confirmed
--
wpa intrepid fails to autenticate
Update. I got another wireless AP for testing and managed connect to it
using WPA without problems. So, in my case the problem was related
somehow to my AP (dlink-624).
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are
Problem with WPA here too after I upgraded to intrepid today. Fresh
syslog attached including some earlier struggling with this issue, after
the latest boot I tried once to connect to ap.
** Attachment added: syslog
http://launchpadlibrarian.net/18200705/syslog
--
wpa intrepid fails to
I forget to give more spesific info:
After upgrading to intrepid I was unable to connect to my AP, so I created new
wireless connection. But no luck for me, when I try to connect to AP nm-applet
shows some spinning animation and after a while appears a dialog which asks a
password for that AP,
Alex is your Open Wifi related with
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/260656 ?
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same problem here. But i even can't connect to access point without any
encription.
Sep 28 16:13:38 xps-ubuntu NetworkManager: info Activation (wlan0/wireless):
connection 'Coder' requires no security. No secrets needed.
Sep 28 16:13:38 xps-ubuntu NetworkManager: info Config: added 'ssid'
root@:# cat /sys/bus/pci/drivers/iwlagn/\:04\:00.0/rfkill\:rfkill0/state
2
From:
http://www.linuxquestions.org/questions/mandriva-30/enable-the-rf-kill-switch-for-ipw2200-592920/#post2973195
rf_kill
read -
0 = RF kill not enabled (radio on)
1 = SW based RF kill active (radio off)
2 = HW
Alex I've attached two logs:
one from my system trying once to connect to a wpa network;
one from a daily LiveDVD from 13/09/2008 to the same network.
--
BUGabundo :o)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net
Linux user #443786GPG key 1024D/A1784EBB
My new micro-blog @
one thing I noticed is that I have no key schema for NM on gconf-editor
it looks like https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/242665
** Attachment added: Screenshot-Configuration Editor -
NetworkManagerApplet.png
Another important thing, this seems to be an issue with the introduction of the
2.6.27 kernel.
I can authenticate just fine if I boot with the 2.6.26 or 2.6.25 kernel images.
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because
** Tags added: 2.6.27
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
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
Dan, it might be very well possible that you experience another bug.
please file a new bug with details about your hardware.
FWIW, intrepid with wpa2 works for me just fine on intel wireless
3945ABG
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this
Reinhard I tested 3 diferent WPA (not WPA2) networks, and suffered the
mention symptoms of this bug and the quasi-dupe #260656.
All with kernel 2.6.27.
With 2.6.25 it was (FINALLY) working after I replaced my faulty intel
wifi card.
If I have the time, I'll make tests with the PPA NM and WPA vs
Reinhard I tested 3 diferent WPA (not WPA2) networks, and suffered the
mention symptoms of this bug and the quasi-dupe #260656.
All with kernel 2.6.27.
With 2.6.25 it was (FINALLY) working after I replaced my faulty intel
wifi card.
If I have the time, I'll make tests with the PPA NM and WPA vs
BUGabundo [EMAIL PROTECTED] writes:
With 2.6.25 it was (FINALLY) working after I replaced my faulty intel
wifi card.
so you needed to replace defective hardware? How does the new hardware
behave with 2.6.27?
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
wpa intrepid fails to
so you needed to replace defective hardware? How does the new hardware
behave with 2.6.27?
It was replace BEFORE 2.6.27 come out.
It worked with older versions of NM and kernel 2.6.25
Once I upgrade I couldnt logon to any Open or WPA protected network anymore.
--
BUGabundo :o)
(``-_-´´)
I'm having the same issue with my senao NL-2511CD card using the hostap
drivers
Here's my /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
This might be a little more helpful
** Attachment added: output of syslog after starting networkmanager via init.d
http://launchpadlibrarian.net/17513738/syslog
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a
please attach the syslog taken _after_ reproducing this (not after
halt). Please attach it as a file and not as tar.gz
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug
and please dont try multiple times. boot, try once, take the syslog and
attach it. Thanks!
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
On Sunday 07 September 2008 01:04:33 Alexander Sack wrote:
please attach your complete syslog taken after reproducing.
I've attached yesterdays FULL log (from boot to halt) where I tried
several times to connect to a WPA protected WiFi network and failed.
also attach your
** Changed in: network-manager (Ubuntu)
Status: Incomplete = New
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
please attach your complete syslog taken after reproducing. also attach
your /etc/network/interfaces.
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because
It would be great if I had an option to turn the RF kill switch off, but I dont.
Pressing FN+F2 doesnt do anything.
I'm some times capable of authenticating, but its just by luck. Depends on the
way it boots up.
Before kernel 2.6.27 it was easier, but on .27 it aint that easy.
--
wpa intrepid
It would be great if I had an option to turn the RF kill switch off, but I dont.
Pressing FN+F2 doesnt do anything.
I'm some times capable of authenticating, but its just by luck. Depends on the
way it boots up.
Before kernel 2.6.27 it was easier, but on .27 it aint that easy.
--
wpa intrepid
definitly not a wpasupplicant problem.
** Changed in: wpasupplicant (Ubuntu)
Status: New = Invalid
--
wpa intrepid fails to autenticate
https://bugs.launchpad.net/bugs/263963
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
54 matches
Mail list logo
