I have ipw3945 and am still having the same problem. network-manager
correctly associates with the AP but does NOT handle the dhclient
correctly.
[EMAIL PROTECTED]:~$ modinfo ipw3945 | grep ^version
version:1.2.2mp.ubuntu1
If I manually run sudo dhclient eth1 after associating to the AP
alrite nothing is fixed to me.
I got a clean install of gutsy.
and i punched in modinfo ipw3945 | grep ^version
and it shows
1.2.2mp
However,
after succesful connection about a few minutes the connection gets lost.
when i do left click on NM and do manual configuration it shows two WIRED
this bug was fixed in ipw3945 driver (version 1.2.2mp.ubuntu1). Thanks
for your feedback. If you have other issues, please look if there are
other bugs already tracking those, otherwise open a new bug.
** Changed in: network-manager (Ubuntu Gutsy)
Status: In Progress = Fix Released
--
confirmed: fixed
thanks
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
After installed todays daily-live build and then installed all updates from
internet (including kernel 2.6.22-11), I was finally able to connect to my
Wireless-G Router.
I dont know what fixed this bug, but at last it is working.
--
[Gutsy]Network Manager Applet can't connect wireless with
Not working for me :( Behaviour seems to be exactly the same -
connection attempted, and then I'm prompted to re-enter the WPA key.
Running 2.6.22-11-generic and all the latest updates. Syslog attached.
** Attachment added: syslog entry for WPA conection
Working normal for me again! Thanks
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
We rolled an updated ipw3945 module which ships a patch that should
normalize association behaviour.
To verify that you have the latest module installed, please do:
# modinfo ipw3945 | grep ^version
version:1.2.2mp.ubuntu1 -- this is the right version
Please test. Thanks,
-
The new version fixed it for me!
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
The whole system seems to struggle if you change the security settings
(in my case from WPA to WPA2). I get a time out in the logs, but
retrying simply goes through the procedure all over again. I'm no
longer asked for a new protocol/password.
On 9/9/07, Alexander Sack [EMAIL PROTECTED] wrote:
Works for me, as well (on Gutsy).
Perhaps we could call this fixed?
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I'm running:
[EMAIL PROTECTED]:~$ cat /proc/version
Linux version 2.6.22-11-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070831
(prerelease) (Ubuntu 4.1.2-16ubuntu1)) #1 SMP Fri Sep 7 05:07:05 GMT 2007
and I've been getting the following messages in my kernel log:
[ 4967.888000] UDP: short
I have encountered this same bug on my home PC with a Edimax USB
(Ralink, rt73 driver).
I am able to connect with WPA from the CLI.
NetworkManager spins for upto 28% and then gives up. So I guess it is
not ipw3945 specific.
Regards
Anand Vaidya
--
[Gutsy]Network Manager Applet can't connect
Working fine for me today, since ipw3945 1.2.2mp.ubuntu1
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Latest update to kernel 2.6.22-11 has fixed this bug for me.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I compiled the new driver as well. Now I can connect to both secured and
unsecured. Thank you very much.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs,
there is an attempted fix for this available in bzr:
https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac
Please test if replacing your current driver with this one helps.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
to get a copy of the source just use:
bzr branch
https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac
to build it you need kernel-headers et al installed and run:
make IEEE80211_IGNORE_DUPLICATE=y SHELL=/bin/bash
** Changed in: network-manager (Ubuntu Gutsy)
Status:
i have a similar problem in feisty: i gat a list of the aviable wireless
networks in natwork-manager bun i connot connect. (it takes foreever and
a day). using manual configuration and static ip connection is no
problem. but then connection ist very very slow. Dell Inspiron 6400 wit
Intel Pro
Thanks Alex, built and tested your tree, and it now works (associates
correctly) with Network manager on an open network.
I'll test with WPA Personal when I'm home. This had been working for me
for some time now, so I'll only post again if it doesn't work.
Thanks so much
--
[Gutsy]Network
I have a Lenovo 3000 N100 with Intel 3945ABG wireless chip. I have
experienced the same problem connecting to unsecured wireless networks
reported by others already: network-manager connected fine under
Feisty, but stopped working when I installed Gutsy. The work-around
reported by others
Still having the same timeout issue as of today with unencrypted
networks, encrypted works fine.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On my Lenovo 3000 N100, my ipw3945 card will connect to wireless
networks (unencrypted and encrypted) under Gutsy, but take 30 seconds to
a minute to connect. This was almost instantaneous under Feisty.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
Running Gutsy with all update up to today and it works for me. It even
reconnects after a resume from S2R. I'm using WPA2 with AES.
Btw: I'm also testing OpenSUSE 10.3 beta2 and they are using the iwl
driver. From comments there it seems the ipw driver is crap ad the iwl
driver is highly
I tried iwl3945, but it creates the interface wlan0_replace - which
isn't seen by network manager. I've tried modinfo to see if I could
specify the interface in the modprobe options, but couldn't find a
related option.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
Alexander Sack: I tried it, just on a live CD (yesterdays build), exactly like
you wrote, even with that optional step, but after I start Network Manager
again, Apport appears and it says Network Manager closed unexpectedly.
I will try to install it on a hdd, yet, and see whether it changes
Alexander Sack: ...When installed on hdd, the Network Manager is not already
crashing after restart, but the wireless disappeared from the NM.
Tried again with and without that optional step.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I didn't get wlan0_replace, but I did have to remove iwl3945 and reinsert it
before I got wlan0 and wmaster0. I suspect that has something to do with
ipw3945 having been loaded previously. So, to recap:
sudo modprobe -r ipw3945
sudo modprobe mac80211
sudo modprobe iwl3945
sudo modprobe -r
It just blew up. I hadn't tested it much, and now I'm having trouble
removing the module, I don't have network access, and everything is
generally screwed up. Apparently wlan0 is in use and the kernel isn't
letting me do much of anything.
--
[Gutsy]Network Manager Applet can't connect wireless
A couple a weeks ago I´ve upgrades to gutsy wireless was not working I
follow the trick to turn on/off the wireless switch while connecting and
this worked 50% of the time.
But I've keep feisty kernel 2.6.20 for the just in case situation and when
booting with this kernel I don't have problem
Well, after a big round of updates of pretty much the entire KDE tree,
knetworkmanager is working fine for me with my WPA2 network and no
longer hangs at 28%, killswitch trick no longer needed either AND the
kwallet integration worked flawlessly too. Have reconnected three times
now and it seems
Someone else with the same problem. Gutsy, upgraded from Feisty, refuses
to connect to any secured network, but will connect just fine with
unsecured networks. Running the latest NM and knetworkmanager on an HP
nx7300 with ipw3945. Connecting to WPA networks didn't work for me in
Feisty either
It looks like everything works fine with iwl3945 (except for the
wireless light on my Thinkpad not lighting up). Is there anything that
prevents that driver being the default?
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You
Alex, you say everything works with iwl drivers using network-manager?
If so, could you please post easy instructions how to test iwl driver
here, so people with this issue can verify if it helps?
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu Gutsy)
Status: Incomplete =
I can confirm this bug.
I am unable to connect to my home router using WPA2 Personal and AES encryption
(SSID broadcast disabled). It was possible in Feisty, but it is not in Gutsy as
far as I remember.
Lastly I tried it in daily-live build 20070831.
I have Intel PRO/Wireless 3945ABG.
--
Here's what I did to use the iwl3945 driver:
sudo modprobe -r ipw3945
sudo modprobe -i mac80211
sudo modprobe -i iwl3945
sudo /etc/init.d/networking restart
Note: iwl3945 will use wlan0 as the interface instead of eth1 (at least
on my hardware). Also, it seems that loading iwl3945 automatically
On Fri, Aug 31, 2007 at 05:55:10PM -, Alex Wauck wrote:
Here's what I did to use the iwl3945 driver:
sudo modprobe -r ipw3945
sudo modprobe -i mac80211
sudo modprobe -i iwl3945
sudo /etc/init.d/networking restart
Note: iwl3945 will use wlan0 as the interface instead of eth1 (at least
On Fri, Aug 31, 2007 at 05:08:34PM -, Petr Nemec wrote:
I can confirm this bug.
I am unable to connect to my home router using WPA2 Personal and AES
encryption (SSID broadcast disabled). It was possible in Feisty, but it is
not in Gutsy as far as I remember.
Lastly I tried it in
After I switched to iwl3945, Network Manager didn't seem to see the new
interface. I think restarting networking did ifconfig wlan0 up, so
maybe that's all that needed to be done for Network Manager to see it.
I didn't have to restart Network Manager. I'll see if I can figure out
how to make
I think this might be related to bug #131553. Note the last comment I
made on that one; it may be that the problems with the 3945 wireless
driver and Network Manager are affecting wired ethernet as well.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I have Dell Latitude D820, and since upgrading to Gutsy from Feisty, I
couldn't even see the wireless network card under System
Administration Network. (it also could not find the ipw3945 driver by
modinfo ipw3945)
As it turns out - I was always selecting the 386 kernel from the Grub
boot menu.
I created a home network with WPA-PSK authentication with a passphrase
and was able to connect to that network. If anyone needs more details
about my laptop (dell latitude d820) hardware or ubuntu setup, please
ask.
I am using
- linux-restricted-modules-generic version 2.6.22.10.11 and
-
I confirm the same bug on a fresh install of Gutsy Tribe 5 on my HP DV
6373 laptop.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I'm still experiencing the bug (bugs?). Rarely it has connected without
any apparent problems, but most times it doesn't work. I haven't had the
time or the chance to explore the problems methodically. My last post
was the first of three times it has connected to the WPA2 network
successfully
Still bugs here as well with WPA Personal.
Plugging in the wired works fine.
Sometimes wireless works and most of the time it doesn't.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because
I have an Acer TravelMate 8210 with the ipw3945 chipset, running Gusty
Tribe 5 fully updated via Update Manager.
I cannot connect to Open or WPA Networks.
I have modprobed, dbus'ed and switched on an off - with no luck.
I have tried network-manager and iwconfig. The networks are visible in
Isn't this a dupe of bug 119563?
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'm not near an open network to try, but are open networks still an
issue? They appeared to be a few days ago last time I tried to use one
(2007-08-23).
Seems the network card associates before NW manager asks it to. Digging
at the ipw3945 sourcecode, there is an option for that behaviour:
Stupidity kicking in... point c) above: my fixwifi.sh script which I
used to unprobe and re-probe the ipw3945 driver had associate=1 set as
a parameter. (DOH!)
I was probably seeing the association because after suspend (which
_should_ work with ipw3945), the wireless often stops working, or the
I can't connect to my open AP from my Thinkpad X60 with Intel ipw3945.
I also see that toggling the wifi kill switch makes things work.
I ran a packet capture and I only see ICMPv6 messages. After I toggle
the kill switch, IPv4 DHCP is performed. I've attached part of the
capture below. Frame
WPA is now working every time for me too (with broadcast SSID).
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Good news: It works now! No problems to connect to an WPA encrypted
network!
At least for my installed Gutsy. For the live-cd (daily-build from
yesterday) I have to reactivate network and wireless and activate it
again. After that I was able to connect to my WPA network.
Tested with my Dell
we should take a close look for tribe-6
** Changed in: network-manager (Ubuntu Gutsy)
Target: tribe-5 = tribe-6
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member
On Mon, Aug 13, 2007 at 10:41:33AM -, Ashton Batty wrote:
I managed to connect today. I did nothing special... I firstly failed to
connect to a unsecured network, but then after that failed, I tried the
WPA2 EAP-TTLS/PAP network, and it connected. NM still doesn't store
anything in the
I managed to connect today. I did nothing special... I firstly failed to
connect to a unsecured network, but then after that failed, I tried the
WPA2 EAP-TTLS/PAP network, and it connected. NM still doesn't store
anything in the gnome-keyring, which seems broken in general. Will
investigate a bit
Don't know if it has anything to do with the problem, but I also get
this error (after the connecting process begins, ie after I switch the
radio button off and on) :
Aug 13 15:45:20 franck-gusty dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth1 for sub-path
I think the problem might be linked with bug number 128116. What makes
me think so is that while nm is trying to connect (until it times out),
latest info displayed in daemon.log is :
Aug 12 14:49:18 franck-gusty NetworkManager: info Activation (eth1) Stage 2
of 5 (Device Configure) complete.
Confirm with IPW3945 on Lenovo N100 0768 with Gutsy Tribe 4. The driver
is not associating at all with the AP, although it can clearly detect
the SSID.
I get a timeout if the network is open and a 'not ready' if the network
is set up with WPA-PSK. More details at bug #131546
--
[Gutsy]Network
I've done a bit more work on this to see if I can get everything in.
If I do a manual configuration, switch off roaming mode and enter the
SSID details by hand then I can get an association and the network
works.
Process to reproduce:
Restart access point.
Restart laptop in roaming mode.
I would just like to add that I have reproduced the following statement
on every boot up:
I would like for everyone to try this. I just turned on my laptop,
opened a terminal and performed and apt-get update without thinking.
Then I noticed that the network manager was still trying to connect.
I still am not able to associate with wireless networks until the kill
switch is toggled after powering up or a suspend/resume cycle. I am
currently running network-manager_0.6.5-0ubuntu9 and using the ipw3945
driver.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
As I said here [1], the applet works well under Tribe4 (both Live-mode
and installed). works well means that it connect to the wireless
network without problems.
Anyway, now It isn't capable of storing the network key. At every boot,
it asks for the key again, and you can understand this is very
ThinkPad X60 with intel chipset here. NetworkManager can't connect to
the wireless network either for me. But it's all set up so I just need
to run
sudo dhclient eth1
in the terminal and I get an IP address and am good to go.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945
Tested with Tribe 4 Desktop-CD in live-mode:
still no luck to connect to an WPA-encrypted network.
(Dell Inspiron 6400 with intel 3945 wireless)
This is a REALLY nasty bug, 'cause with feisty the intel 3945 wireless
chip is the best supported wireless-chip at all, supports every
encryption.
--
I would like for everyone to try this. I just turned on my laptop,
opened a terminal and performed and apt-get update without thinking.
Then I noticed that the network manager was still trying to connect.
The weird thing is that the update downloaded. So I figured that I
would try a apt-get
On Wed, Aug 08, 2007 at 02:23:57PM -, Chris Lovett wrote:
no, network-manager 0.6.5-0ubuntu9 still has not fixed the problem for
me. i just waited for well over a minute to connect to my unencrypted
network and finally had to toggle my switch off and on for it to work.
as soon as i toggle
On Wed, Aug 08, 2007 at 11:02:35PM -, Peter Clifton wrote:
NAK - Still broken here.
ii network-manager 0.6.5-0ubuntu9 network management
framework daemon
ii network-manager-gnome0.6.5-0ubuntu8 network management
framework (GNOME frontend)
(Is
On Thu, Aug 09, 2007 at 04:48:22AM -, TorenC wrote:
I have a Dell D820 with an intel 3945, and under gutsy I also have to
switch my wireless switch on and off to connect with network manager.
I'm running current gutsy with network-manager 0.6.5-0ubuntu9. This
happens _every_ time I try to
On Thu, Aug 09, 2007 at 05:50:59AM -, Ashton Batty wrote:
Still no luck today. It is doing better than yesterday... actually gets
a key now, whereas before it would never manage to get a key. But now it
times out while trying to associate. (Check the log excerpt)
Can you try WPA-PSK as
Alexander, my ssid is set to broadcast. The network is also open.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Sorry, I have no control over the network, and must use EAP-TTLS/PAP.
The key type can either be AES-CCMP or TKIP.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of
Still no luck today. It is doing better than yesterday... actually gets
a key now, whereas before it would never manage to get a key. But now it
times out while trying to associate. (Check the log excerpt)
** Attachment added: relevant (hopefully) excerpt of daemon.log
I seem to be doing better since the update... still had a problem last
night, but things are going swimmingly.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Lenovo T61, ipw3945, network-manager 0.6.5-0ubuntu9 won't connect to an
open AP. It associates fine, but doesn't get an address via DHCP. I
run sudo dhclient3 eth1 manually as a workaround.
Here's an interesting message that appears in /var/log/user.log when I
try to connect with Network
I managed to connect for a few seconds!
All I had to do was to pull the plug from my fonera, and I was able to connect
to my WRT54GL running DD-WRT with WPA2. It seems the open network on the fonera
kept messing things up, as NM would connect to it while trying to connect to
WPA2. Now the only
I have a Thinkpad T60 with Kubuntu Gutsy just installed and fully
updated. I cannot connect to my college's unsecured wireless network
unless I use the RF kill-switch on the front to toggle the device off
and then on again while it attempts to connect. According to daemon.log
(which I have
This was confirmed as fixed for two people, Chris still experienced it.
Chris, can you please check with 0.6.5-0ubuntu9 again?
Moving over to Tribe 5, this is not a blocker any more since it seems to
work now.
** Changed in: network-manager (Ubuntu Gutsy)
Target: tribe-4 = tribe-5
--
No luck for me either. Network manager still doesn't want to connect to
wpa2-enterprise network, (works fine in Fedora 7, so I know network
manager *can* do it). I never got the various workarounds to work
either, though I have not had trouble using wpa_supplicant manually.
I'll try again tomorrow
My wireless seems to work fine with Wicd, which tells me that my problem
(on Feisty) was definitely with NetworkManager, not anything else. I'd
really like this fix to make it back to Feisty, since I like
NetworkManager more than Wicd.
--
[Gutsy]Network Manager Applet can't connect wireless with
network-manager 0.6.5-0ubuntu9 should fix wpa for ipw3945 ... if it
doesn't for you please let us know.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs,
network-manager 0.6.5-0ubuntu9 should fix wpa for ipw3945 ... if it
doesn't for you please let us know
and what about Feisty, is it the same problem, and if yes, will the
package be available for Feisty too?
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
no, network-manager 0.6.5-0ubuntu9 still has not fixed the problem for
me. i just waited for well over a minute to connect to my unencrypted
network and finally had to toggle my switch off and on for it to work.
as soon as i toggle the switch it connects immediately.
--
[Gutsy]Network Manager
NAK - Still broken here.
ii network-manager 0.6.5-0ubuntu9 network management
framework daemon
ii network-manager-gnome0.6.5-0ubuntu8 network management
framework (GNOME frontend)
(Is there an update pending for network-manager-gnome which is needed,
and I've
I have a Dell D820 with an intel 3945, and under gutsy I also have to
switch my wireless switch on and off to connect with network manager.
I'm running current gutsy with network-manager 0.6.5-0ubuntu9. This
happens _every_ time I try to connect to my open wireless network (I
don't have any
Please try the latest gutsy network-manager packages (version
0.6.5-0ubuntu8). They have a lot of related fixes.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of
Still not working for me. I just did an upgrade and rebooted.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
network-manager is still 0.6.5-0ubuntu7 , network-manager-gnome is
0.6.5-0ubuntu8 .
but no improvements.
this bug is really nasty
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received this bug notification because
I also can confirm it still doesn't work. In fact prior to today's
gutsy update I was able to connect to my wireless network (WEP) although
it was way slow. But now I cannot connect wireless at all (Intel 3945).
Tried several workarounds and reboots and the result is always the same.
The gray
Joy, at least for me. There's a new gutsy network-manager update out
there (had to click check in update-manager to see it). My 3945
wireless is back to working now.
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You received
Any chance the fix for this will make it back into Feisty? Or does the
fact that I'm seeing the same problem in Feisty since a few weeks ago
mean that something else is wrong?
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You
Shoofy, like you, I started experiencing this problem on Feisty a few
weeks ago (see earlier comment and also-affects).
Do we know whether this is really the same problem?
--
[Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
https://bugs.launchpad.net/bugs/121439
You
with network-manager 0.6.5-0ubuntu9 it takes approx. 30 secs to connect
to my WPAed network and still the key is not stored in keyring, although
it is asking for the master key every time. but i think this is another
problem as happens with other stuff like connecting to servers as well.
besides
A few additional data points:
On my notebook (Dell Latitiude D820, fully updated gutsy as of August 1
2007, kernel 2.6.22-9-generic):
The wireless kill switch trick works (documented in comments on this bug
already)
swapping out the 3945 card with an Atheros card results in
NetworkManager
I can now (from when I could ? I don't know) connect to an wep encrypted
network with NetworkManager, without switching the kill switch button.
But I still need to do that with an unencrypted one.
I use Gutsy up to date :
- kernel : 2.6.22-9-generic
- Network manager : 0.6.5-0ubuntu7
- Network
On Thursday 02 August 2007 17:15, yostral wrote:
I can now (from when I could ? I don't know) connect to an wep encrypted
network with NetworkManager, without switching the kill switch button.
But I still need to do that with an unencrypted one.
I am also now in the same boat after
I can report an improvement with WPA - 0.6.5-0ubuntu7/2.6.22-8-generic
reliably connects on the third attempt.
The first attempt (automatic at login) gives a prompt for my WPA key. If
I cancel this, then choose my network from the list, it connects
correctly without prompting (I use pam_keyring,
hi,
after some canceling and inserting the key several times i finally get a
connection. still have to find out the exact steps...
but there seems to be some general problem with the keyring. maybe this
is related. at least for me it doesn't save any keys. not for nm-applet
or any other program.
Jon Anderson [EMAIL PROTECTED] writes:
Anyway, do other people see this behaviour (connecting to open networks
automagically)?
I assumed that this was a 'feature' of NM? - So yes, I notice this as
well from time to time.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--
I assumed that this was a 'feature' of NM? - So yes, I notice this as
well from time to time.
But I'm not talking about NM... since upgrading to Gutsy, my laptop
connects to random open networks before NM is even involved in the
process:
- before I log in (my KNetworkManager settings are in
I'm also seeing this on Gutsy. iwconfig shows
eth1 IEEE 802.11g ESSID:Belkin54g
which is my neighbour's open access point, not my WPA one - I'm
currently connected by Ethernet from eth0, and there is no mention of
this ESSID in /var/log/daemon.log.
--
[Gutsy]Network Manager Applet can't
1 - 100 of 157 matches
Mail list logo
