I think I am seeing this bug in the ubuntu eee 8.04.1 edition.
Surely this is fixed now?
Wireless works fine apart from wpa2 which gets a timeout from wpa_supplicant.
I have switched to wpa on my network now as a workaround and this is fine.
This is on a eee 901 so should be reproducable by
confirmed on hardy,
wpa2 peap doesn't connect
wpa psk doesn't work
ipw2100 chipset
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
ipw2200 has been confirmed t owork for wpa psk (which was the initial
reporters claim) in hardy. please file individual bugs if you see it for
other chipsets.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Released
--
WPA2 Personal wireless networks don't work without
this problem still exists in the Hardy Beta! Help..
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I tried the latest release of wicd and it fixed my problem of Ubuntu
Gutsy not remembering WPA2 and pw, and resetting to WPA upon each boot.
It has been a real pain.
Wcid has been a great fix so far. Please consider including it in the
next release.
--
WPA2 Personal wireless networks don't work
A number of my associates use wicd, and they have issues connecting to
WPA Enterprise networks with PEAP with it. I'll ask them to file bugs.
Also, there are a number of issues with wicd - among them, it displays
your password in cleartext as you type it in, only censoring it once
you've
Please follow these instructions to install and use wicd (wifi network
manager):
http://wicd.sourceforge.net/download.php
Please let us know if wifi and WPA2 encryption works better using wicd
--
WPA2 Personal wireless networks don't work without manual configuration
Same problem here with Toshiba Qosimo F45 with Intel 4965AGN chipset and
Gutsy 7.10 with WPA2 Personal and AES encryption and broadcast SSID and
automatic configuration (DHCP). Anytime I shut down computer or even
log off as user and back on, I find that the laptop has defaulted to WPA
with a 40
I was able to solve this problem by installing Debian packages and the
latest ipw2200 1.2.2 as follows.
Download the ipw2200 1.2.2 driver from sourceforge and 3.0 firmware and install
it.
Download the following files from Debian distrib packages:
libiw28_28-1_i386.deb
On Gutsy, bug #140422 could influence.
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
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 have to dissent. This is not a Ubuntu bug but a networkmanager bug.
I have experienced this behavior with my dell inspiron 1520 which uses
an IPW3945 chipset in two different distros. Arch and Debian Sid. The
problem is in networkmanager. a workaround is to try to use the command
line + sudo
Hi
Stephen Hemminger wrote:
Problem still exists when attempting to use WPA2 with ipw2200 on Gusty.
Please fix or forward upstream rather than ignoring.
FWIW, all the WPA networks I've tried have worked fine for me in gutsy
with ipw2200. What does /var/log/syslog say when you attempt to join
Problem still exists when attempting to use WPA2 with ipw2200 on Gusty.
Please fix or forward upstream rather than ignoring.
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug notification because you are a
Reopened according to Stephen Hemminger.
I think NM 0.7. that is supposed to bring better WPA support is soon to be
released and this will be fixed with that release.
** Changed in: network-manager (Ubuntu)
Status: Fix Released = Confirmed
--
WPA2 Personal wireless networks don't work
network manager has come a long way since feisty. I assume this issue is
fixed not in gutsy. Please reopen if you still see _this_ particular
issue in latest gutsy network-manager (0.6.5-0ubuntu15).
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix
This still appears to be a problem in gutsy (even though it was never
really a problem for me in feisty).
[EMAIL PROTECTED]:~$ dpkg -l | grep network-manager
ii network-manager0.6.5-0ubuntu14
network management framework daemon
ii
If you still see this issue, please attach your /var/log/syslog
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This has been taken care of upstream, we can only wait for Gutsy.
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed = Confirmed
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug notification
Confirming the original report - I think. It took me quite some time to
figure out how to get WPA working. What I find is that both
knetworkmanager (and nm-applet) show my WPA access point as WEP at
first, as does iwlist wlan0 scan. If I select that network both tools
will prompt me for a WEP
Update: putting the command iwpriv wlan0 wpa 1 in a startup script
allows NetworkManager to get the correct encryption type the first time.
I have a prism2.5 card (NICID 8013), using the hostap_pci driver and up-
to-date firmware. Perhaps wpa_supplicant knows to put the driver in
this mode?
--
I have to fifth this problem, got a HP Pavillion with a 3945ABG Network
card. Denies totaly to my WPA2 network.
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug notification because you are a member of Ubuntu
I have to third this, because I am having a problem, as others are,
connecting to a WPA2 network using Feisty. My understanding is that it
is not that a single wireless card is affected. I have a BCM4318 card,
and while I can connect to non-secure networks, I can't connect to my
own WPA2
Well if Pennypacker is thirding this, then I must be fourthing. Just
today I saw another T42 with the 2200 chipset unable to get on the WPA
network.
--
WPA2 Personal wireless networks don't work without manual configuration
https://bugs.launchpad.net/bugs/106129
You received this bug
I have seen at least two systems with the following chipset exhibit this
behavior, but have been unable to test the manual workaround specified
in this bug.
04:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG
Network Connection (rev 05)
--
WPA2 Personal wireless networks don't
I second this, not possible to get WPA2 to work in Feisty, and here is my
hardware info:
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
--
WPA2 Personal wireless networks don't work without manual configuration
25 matches
Mail list logo
