A number of people have reported difficulties in using WPA2 with
openSUSE. I have no idea why it works, but the “fix” is to use YaST =>
Software Management to reload the same kernel from the repos.
Magically, WPA2 works with AES or TKIP+AES encryption.
Larry
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hmmm… well that’s weird. I haven’t had to do that on any of
three laptops (Latitude D620, Latitude D630, HP dv6000) for my home WPA2
network, but this is still interesting. Have you noticed a changing
version at all in ‘uname’ before vs. after your reboot?
Good luck.
Larry Finger wrote:
> A number of people have reported difficulties in using WPA2 with
> openSUSE. I have no idea why it works, but the “fix” is to use YaST =>
> Software Management to reload the same kernel from the repos.
> Magically, WPA2 works with AES or TKIP+AES encryption.
>
> Larry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJZVJa3s42bA80+9kRAo/CAJ9kFXYgd85k8E8m8c4tkgOS0VmweQCaAvdd
BQ2UJTI/kT246rWo5h9kvoY=
=tXkU
-----END PGP SIGNATURE-----
ab@novell.com wrote:
> Hmmm… well that’s weird. I haven’t had to do that on any of
> three laptops (Latitude D620, Latitude D630, HP dv6000) for my home WPA2
> network, but this is still interesting. Have you noticed a changing
> version at all in ‘uname’ before vs. after your reboot?
Absolutely none. The date on the kernel is 12/4/2008. The only point
that might be appropriate is that I upgraded using the NET install
disk; however, I just checked another machine that was installed over
the network and its kernel has the same date and time as the one I
just reinstalled.
Larry
Well this worked for me. I can now connect BUT I still have very erratic signal strength.
On 2009-01-07, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> A number of people have reported difficulties in using WPA2 with
> openSUSE. I have no idea why it works, but the “fix” is to use YaST =>
> Software Management to reload the same kernel from the repos.
> Magically, WPA2 works with AES or TKIP+AES encryption.
>
Larry, it does not works for me.
It works only if I connect without protection.
Tried with wep, wpa-personal 1/2.
My wifi router has options : no-protection, wep, wpa-psk( 256 bit ),
wpa-aes ( 256 bit ). Tried with all but the only that works
is without protection.
Tried to reinstall kernel from dvd and again to reinstall
it from oss/repository ( download.opensuse.org )
OpenSuSE version is 11.1, with kernel : 2.6.27.7-9-pae
Wifi card is : Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express
Adapter (rev 01)
I can see correctly the wlan and wifi networks around.
iwconfig is :
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.437 GHz Access Point:
Not-Associated
Bit Rate:12 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality=7/100 Signal level:-90 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
with iwevents I try to connect with NetworkManager and I just see
events :
Waiting for Wireless Events from interfaces…
16:58:18.514751 wlan0 Scan request completed
16:58:24.543143 wlan0 Scan request completed
16:58:30.546265 wlan0 Scan request completed
16:58:36.550232 wlan0 Scan request completed
16:58:42.560157 wlan0 Scan request completed
16:58:43.594287 wlan0 Scan request completed
16:58:51.197451 wlan0 Scan request completed
16:59:51.202382 wlan0 Scan request completed
Do you have any idea
Best Regards
R
You actually have a problem with wpa_supplicant. I was also having a hard time setting that thing, but be persistant.
Find here posts about wpa_supplicant configuration & madwifi.
I believe I made some posts in wireless section. I have same atheros and I was bleeding with it in the beginning. But people here helped me, so I suggest you look at my posts.
Other guy also wrote complete solution for Atheros.
Make a config file (you will find here how - I am now at work on another machine) and do something like:
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
beli0135 wrote:
> You actually have a problem with wpa_supplicant. I was also having a
> hard time setting that thing, but be persistant.
>
> Find here posts about wpa_supplicant configuration & madwifi.
> I believe I made some posts in wireless section. I have same atheros
> and I was bleeding with it in the beginning. But people here helped me,
> so I suggest you look at my posts.
> Other guy also wrote complete solution for Atheros.
>
> Make a config file (you will find here how - I am now at work on
> another machine) and do something like:
>
> wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
It is not necessarily a wpa_supplicant problem. If you read the
thread, you will see that I had a failure with kernel 2.6.27.7-9, but
that 2.6.28 worked. Both kernels were using EXACTLY the same
wpa_supplicant code and configuration. When I refreshed the standard
kernel from the repo, then it worked too.
Larry
On 2009-01-09, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> beli0135 wrote:
>> You actually have a problem with wpa_supplicant. I was also having a
>> hard time setting that thing, but be persistant.
>>
>> Find here posts about wpa_supplicant configuration & madwifi.
>> I believe I made some posts in wireless section. I have same atheros
>> and I was bleeding with it in the beginning. But people here helped me,
>> so I suggest you look at my posts.
>> Other guy also wrote complete solution for Atheros.
>>
>> Make a config file (you will find here how - I am now at work on
>> another machine) and do something like:
>>
>> wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
>
> It is not necessarily a wpa_supplicant problem. If you read the
> thread, you will see that I had a failure with kernel 2.6.27.7-9, but
> that 2.6.28 worked. Both kernels were using EXACTLY the same
> wpa_supplicant code and configuration. When I refreshed the standard
> kernel from the repo, then it worked too.
>
> Larry
it seems, it seems it works.
it was wpa1 not 2
Good afternoon,
I do have exactly the same problem with the wpa_supplicant and an intel 3945 wireless lan card. I wrote a script for the wpa_supplicant that worked very well with 10.2 but since I installed 11.1 I can’t setup WPA2 Personal connection anymore. WPA enterprise connections are Ok. I’ve tried all the solution described in here but not chance. Does anybody know the reason why?
It drives me crazy
Thanks:(
Thomas A wrote:
> Good afternoon,
> I do have exactly the same problem with the wpa_supplicant and an intel
> 3945 wireless lan card. I wrote a script for the wpa_supplicant that
> worked very well with 10.2 but since I installed 11.1 I can’t setup WPA2
> Personal connection anymore. WPA enterprise connections are Ok. I’ve
> tried all the solution described in here but not chance. Does anybody
> know the reason why?
> It drives me crazy
I guess you tried reloading the kernel and the supplicant. Several of
us found that WPA2 did not work until we did.
The only other suggestion is to switch to NetworkManager and add your
new connection. On my system, once the kernel was reloaded, the device
connected with WPA2 Personal using the same parameters as had been
input for WPA Personal.
BTW, none of my connections have used Enterprise.
Larry
Thanks for the answer. I did use the networkmananger but had to remove it, due to problems with the dhclient. The dhclient didn’t want to set a default route. But I’m not the only one with this problem.
I’d prefer to use the wpa_supplicant with the config-files, since I do not use X very often. So I still look for an answer. Thanks again.
Thomas
I work with psk2 on suse 10.3 no problems
acer laptop with broadcom wireless adapter
not yet testet with 11.1
but it is important no wireless connection definiton on the network / netcard wireless part of yast
( default entries on the [verbindungs einstellungen ])
on this way i can see all wireless networks around me. and it works only with ifup mode
Sorry WPA2