** Changed in: network-manager
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/292054
Title:
Some drivers take too long to associate (Was: network-manager 0.7
always
Looks my Dell Vostro 1500 has smae issue connecting to WPA2 Enterprise
network. Any workaround?
Apr 8 15:03:04 DeepBlue wpa_supplicant[1287]: Failed to initiate AP scan.
Apr 8 15:04:57 DeepBlue NetworkManager: info Activation (wlan0) starting
connection 'Auto Corporate_WiFi'
Apr 8 15:04:57
I have a similar but slightly different issue. wpa_supplicant
associates fine, but network-manager times out waiting for dhclient to
finish. If I run dhclient manually (from /etc/network/interfaces) then
everything is fine.
NetworkManager: info Activation (wlan0) starting connection 'Auto
** Branch linked: lp:ubuntu/network-manager
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: network-manager (Ubuntu)
Assignee: Kevint (ktreadwell) = Alexander Sack (asac)
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a
** Changed in: network-manager (Ubuntu)
Assignee: Alexander Sack (asac) = Kevint (ktreadwell)
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a
I have opened bug #337311 regarding the ath5k performance problems in
Jaunty. I have re-tested today and it appears that some performance loss
has already been fixed upstream in compat-wireless-2009-03-03. I do not
know when this upstream version will appear in the Jaunty kernel.
--
Some drivers
network-manager roams to (none) ((none)) has already been reported as
bug #291760, however it appears to be a harmless message related to
losing the connection to the AP (at least with the latest ath5k driver).
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for
On Thu, Jan 29, 2009 at 01:59:26PM -, Chris Bainbridge wrote:
There also seems to be some new problem with Jaunty, I'm seeing the following
error repeated every so often: NetworkManager: debug [1233236271.814432]
periodic_update(): Roamed from BSSID 00:1D:68:0A:xx:yy (nameofwap) to (none)
** Changed in: network-manager
Status: Confirmed = In Progress
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just realised that when I tested the jaunty kernel I didn't upgrade
linux-restricted-modules, so I was only testing ath_pci. To clarify:
With 2.6.28-6 kernel and ath5k module, I see the slow bandwidth and high
pings noted above. It might be something to do with this error in the
logs ath5k
This seems to be the crucial bit in the logs:
1230757793.729916: RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
1230757793.730072: RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
1230757793.730156: Wireless event: cmd=0x8b15 len=20
1230757793.730175: Wireless event: new
Alex,
At your suggestion I tried linux-image-2.6.28-6-generic. I no longer see
the very long delay that leads to wpa_supplicant timing out and
blacklisting the AP leading to 60s association.
Jaunty ath5k is still slow though - comparing ath5k to zd1211rw over
repeated runs I get a statistically
I take back the statement about the roaming causing packet loss - even
with the Zydas card NetworkManager reports a roam to none for about 6
seconds, but it doesn't seem to actually cause any problems.
However, the throughput of ath5k is very poor. I'm running ping whilst
transferring a single
I see the symptoms of this bug, but usually only when I'm on an 802.1x
network (or at least substantially more frequently). Running sudo
killall -9 wpa_supplicant sometimes gets it behaving better, but I
don't have anything concrete to back that up, and sooner or later the
behavior crops up again,
On Wed, Jan 28, 2009 at 05:19:16PM -, Jeremy Nickurak wrote:
I see the symptoms of this bug, but usually only when I'm on an 802.1x
network (or at least substantially more frequently). Running sudo
killall -9 wpa_supplicant sometimes gets it behaving better, but I
don't have anything
On Tue, Dec 30, 2008 at 01:43:37AM -, Chris Bainbridge wrote:
I tested again with a different AP, open AP so no WEP or WPA, borrowed
this AP just for testing so no other users, AP next to test PC (64/70
signal). Using wpasupplicant-0.6.4-2 and network-
manager-0.7-0ubuntu1~nm1~intrepid1.
I tested again with a different AP, open AP so no WEP or WPA, borrowed
this AP just for testing so no other users, AP next to test PC (64/70
signal). Using wpasupplicant-0.6.4-2 and network-
manager-0.7-0ubuntu1~nm1~intrepid1. Config in /etc/NetworkManager so no
front-end delay. Hopefully this
On Mon, Dec 22, 2008 at 03:00:39PM -, Chris Bainbridge wrote:
The bug seems to be in some interaction to do with NetworkManager or the
DBUS interface. If I put a WEP config in /etc/wpa_supplicant/ and do:
/sbin/wpa_supplicant -d -t -iath0
-c/etc/wpa_supplicant/wpa_supplicant.conf
Then
** Bug watch added: w1.fi/bugz/ #291
http://w1.fi/bugz/show_bug.cgi?id=291
** Also affects: network-manager via
http://w1.fi/bugz/show_bug.cgi?id=291
Importance: Unknown
Status: Unknown
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA
** Changed in: network-manager
Status: Unknown = Confirmed
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The bug seems to be in some interaction to do with NetworkManager or the
DBUS interface. If I put a WEP config in /etc/wpa_supplicant/ and do:
/sbin/wpa_supplicant -d -t -iath0
-c/etc/wpa_supplicant/wpa_supplicant.conf
Then wpa_supplicant will associate in just over 10 seconds. Log
attached.
I just found bug #259157 ... it has some similar reports to this one.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After some testing, I think this is a wpa_supplicant problem. If I
configure /etc/network/interfaces and use ifup then the time from
typing that command to actually having an IP address is around 15
seconds. If I use NetworkManager then the time is over 1 minute. It
looks as though wpa_supplicant
** Attachment added: Fast interface up with ifup - this is how it should be
http://launchpadlibrarian.net/20622792/wifi-fast
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug
It would be useful if someone else could confirm this by configuring
/etc/network/interfaces and comparing the start time to NetworkManager.
It seems to be a different issue to the kernel regression reported by
jasonwc. Alternatively the following commands will do the same if you
use WEP, the
jasonwc, can you please check that the timeout is now 60s?
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package network-manager -
0.7~~svn20081018t105859-0ubuntu1.8.10.1
---
network-manager (0.7~~svn20081018t105859-0ubuntu1.8.10.1) intrepid-proposed;
urgency=low
* fix LP: #292054 - Some drivers take too long to associate (Was:
network-manager 0.7 always
Alexander,
I can confirm that the 0.7~~svn20081018t105859-0ubuntu1.8.10.1 update
waits 60 seconds before giving a timeout error. Through my testing I
have discovered two separate bugs, the first of which is mitigated by
this package.
1. Some drivers take too long to associate with the 2.6.27
PEAPv0/EAP-MSCHAPv2 and EAP-TTLS/MSCHAPv2 both connect every time under
kernel 2.6.27. It just takes longer than 2.6.24. If you would like me to
test any other configurations I have a FreeRADIUS at my disposal.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for
That should read FreeRADIUS server.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I gave the wrong bug # earlier. The bug I reported was Bug #307622
(Ubuntu fails to reliably associate with WPA2-Enterprise networks using
either the WG511T (AR5212) or Intel 4965AGN wireless chipsets with
2.6.27 kernel).
--
Some drivers take too long to associate (Was: network-manager 0.7
I'm still having timeout problems with the new package. PEAPv0/MSCHAPv2
will occasionally connect whereas EAP-TLS consistently fails to connect.
The bizarre part is that the majority of the time the RADIUS server
doesn't even get a request for authentication, and when it does get a
request, the
The workaround is not working for me.
I have to wait more time before being asked again for data, but I still receive
the same message.
In attach my daemon.log
Thank you
Haldo
** Attachment added: daemon.log
http://launchpadlibrarian.net/20142760/daemon.log
--
Some drivers take too long
Alex today on wpa entreprise it seems to be working.
No idea why it wouldnt connect to wpa shared.
Sorry for the noise.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug
On Fri, Nov 28, 2008 at 06:08:32PM -, BUGabundo wrote:
Please revert this.
network-manager (0.7~~svn20081018t105859-0ubuntu2) jaunty; urgency=low
just broke my wpa.
Now it wont connect and just times out
There is nothing in this upload that could make such issues appear for
your. I
** Description changed:
+ Verify:
+ 1. ensure that you are affected: NM connect times out after 25 seconds +
wpasupplicant takes more than ~25 seconds to connect manually
+ 2. test that new package either succeeds or takes 60 seconds before giving up.
+
+
Binary package hint: network-manager
** Changed in: network-manager (Ubuntu)
Status: Triaged = Fix Committed
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs,
upload SRU: network-
manager_0.7~~svn20081018t105859-0ubuntu1.8.10.1_source.changes to ubuntu
/intrepid-proposed
** Changed in: network-manager (Ubuntu Intrepid)
Status: Triaged = In Progress
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA
This bug was fixed in the package network-manager -
0.7~~svn20081018t105859-0ubuntu2
---
network-manager (0.7~~svn20081018t105859-0ubuntu2) jaunty; urgency=low
* fix LP: #292054 - Some drivers take too long to associate (Was:
network-manager 0.7 always asks for WPA passphrase);
Accepted network-manager into intrepid-proposed, please test and give
feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed
for documentation how to enable and use -proposed. Thank you in advance!
** Changed in: network-manager (Ubuntu Intrepid)
Status: In Progress = Fix
Please revert this.
network-manager (0.7~~svn20081018t105859-0ubuntu2) jaunty; urgency=low
just broke my wpa.
Now it wont connect and just times out
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You
worksforme
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm getting the same problem @ work, when connecting to a WPA2-PSK PEAP.
Just for your information, I tried Fedora 9 Live (usb), and I've got the same
problem.
** Also affects: network-manager (Fedora)
Importance: Undecided
Status: New
--
Some drivers take too long to associate
I couldn't get NetworkManager+knetworkmanager to connect at all to my
wifi network (using thinkpad t42 with atheros card). It looked like
wpa_supplicant was timing out. Upgrading to the PPA packages fixed the
issue.
@BUGabundo: you can set mode using 'iwpriv ath0 mode x' where x is an
integer
I have a similar issue (WPA always/often asking for passphrase).
It also seems to result in WLAN access not working at all after a
suspend. This is a regression bug from hardy.
I have a thinkpad X31 with an atheros card.
--
Some drivers take too long to associate (Was: network-manager 0.7
Alex not sure if this is where I should post this.
This are logs of trying to connect to a FON WPA2 network
FYI I have no trouble with other domestic WPA/WPA2 networks. Just
yesterday NM connected just after GDM started.
I'm inclined to think that some of this time outs (here and on bug
272185)
** Attachment added: wpa_suplicant
http://launchpadlibrarian.net/19377185/wpa_suplicant
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a member of
BUGabundo - I suspect you're onto something.
My problems relate to our corporate network where the authentication is
backed by our active directory domain and it works fine on my home PSK
network. Of course, we also have a load of APs in the office to ensure
coverage of the entire building and
if you see this on some APs (but not all), could you check whether your
AP is in A, G or N mode?
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
https://bugs.launchpad.net/bugs/292054
You received this bug notification because you are a
MarkS, could you try to create a wireless connection in connection-
editor and set a fixed BSSID (for any of those 3 APs) and see if it
doesnt roam anymore? Maybe that helps?
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
@asac AFAICR they are all G networks.
At my universaty some APs also have A networks, but I cant really tell to what
I'm connecting
Is there a way via driver or NM to select the protocol?
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack (asac)
** Changed in: network-manager (Ubuntu Intrepid)
Assignee: (unassigned) = Alexander Sack (asac)
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
we should give them more time. like the ~network-manager PPA package
currently proposes.
This issue is about atheros, but we also have bug 263963 which is about
iwl drivers; and dont forget the WPA-Enterprise issues we solved with
such a timeout patch.
** Summary changed:
- network-manager 0.7
nominating for intrepid updates ... though that patch is already
nominated to fix WPA Enterprise PEAP Use-Case (like bug 272185)
** Changed in: network-manager (Ubuntu Intrepid)
Importance: Undecided = High
Status: New = Triaged
Target: None = intrepid-updates
--
Some drivers
The NetworkManager is disabling my ethernet card and making it
impossible to login to Intrepid, and I wonder if this is a related
problem. The ethernet works fine in single user recovery mode, but it
has been impossible to log into my machine for three days. I am
desperate.
uname -a (in single
David, ethernet card issues are clearnly not covered in this bug. open
new bugs if you are unsure instead of adding stuff to whatever thing
sounds related. Thanks.
--
Some drivers take too long to associate (Was: network-manager 0.7 always asks
for WPA passphrase)
57 matches
Mail list logo
