Need help with WLAN on Eee PC 1000H
Hello!
I need your help with my WLAN on a Asus Eee PC 1000H. It has a Ralink WiFi card --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 01:00.0 Network controller [0280]: RaLink Device [1814:0781] Subsystem: RaLink Device [1814:2790] Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at fbef0000 (32-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: rt2860 Kernel modules: rt2860sta --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- Then I configured the rpmfusion repository and installed the rt2860 package. There was a small caveat - I had to do "iwpriv ra0 radio_on" in order to do anything related with WLAN, but afterward scanning was possible. But I can't connect my AP using Network Manager. Basically I see those two lines in wpa_supplicant.log Trying to associate with 00:18:f3:85:6a:31 (SSID='memphis' freq=2437 MHz) Authentication with 00:00:00:00:00:00 timed out. NM keeps asking me for a password, but my input is definitely correct. So I thought NM messes things up (as was my experience with my old notebook) and I tried to get WLAN running using iwconfig + wpa_supplicant configuration directly. Here is my wpa_supplicant.conf I used. --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="memphis" scan_ssid=1 psk="myverysecretpassword" } --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- But it did not work either, the Eee PC still could not connect to the AP. The only way I can establish a WLAN connection is to compile the rt2860 driver from the Ralink homepage (http://www.ralinktech.com/ralink/Home/Support/Linux.html) without any patches and configure it *only* for wpa_supplicant support, not NM support! Then and only then I can connect to my AP using WPA *but* I have to use iwpriv command to set the encryption password! (iwpriv set WPA=secret) I've ran out of ideas what else to try. Do you see a point I'm obviously missing? I've search the net, but it seems to work for everybody else, contradicting my experience. Any help would be *very* appreciated. -- bye Adalbert _______________________________________________ Fedora-laptop-list mailing list Fedora-laptop-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-laptop-list |
Need help with WLAN on Eee PC 1000H
Hello!
Last week I wrote to the fedora-laptop list, bo nobody there was able to help me. I need your help with my WLAN on a Asus Eee PC 1000H. It has a Ralink WiFi card --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 01:00.0 Network controller [0280]: RaLink Device [1814:0781] ********Subsystem: RaLink Device [1814:2790] ********Flags: bus master, fast devsel, latency 0, IRQ 19 ********Memory at fbef0000 (32-bit, non-prefetchable) [size=64K] ********Capabilities: <access denied> ********Kernel driver in use: rt2860 ********Kernel modules: rt2860sta --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- I configured the rpmfusion repository and installed the rt2860 package. There was a small caveat - I had to do "iwpriv ra0 radio_on" in order to do anything related with WLAN, but afterward scanning was possible. But I can't connect my AP using Network Manager. Basically I see those two lines in wpa_supplicant.log Trying to associate with 00:18:f3:85:6a:31 (SSID='memphis' freq=2437 MHz) Authentication with 00:00:00:00:00:00 timed out. NM keeps asking me for a password, but my input is definitely correct. So I thought NM messes things up (as was my experience with my old notebook) and I tried to get WLAN running using iwconfig + wpa_supplicant configuration directly. Here is my wpa_supplicant.conf I used. --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ * * * * ssid="memphis" * * * * scan_ssid=1 * * * * psk="myverysecretpassword" } --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- But it did not work either, the Eee PC still could not connect to the AP. The only way I can establish a WLAN connection is to compile the rt2860 driver from the Ralink homepage (http://www.ralinktech.com/ralink/Home/Support/Linux.html) without any patches and configure it *only* for wpa_supplicant support, not NM support! Then and only then I can connect to my AP using WPA *but* I have to use iwpriv command to set the encryption password! (iwpriv set WPA=secret) Did you succeed in using WLAN with F10 on Eee PC 1000H and if yes - how did you do it? Do you have an idea how to convince Ralink's chip to behave "normally"? I've ran out of ideas what else to try. Do you see a point I'm obviously missing? I've search the net, but it seems to work for everybody else, contradicting my experience. Any help is *very* appreciated. -- bye Adalbert -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
On Mon, Jan 12, 2009 at 10:01:39PM +0100, Adalbert Prokop wrote:
> Hello! > > Last week I wrote to the fedora-laptop list, bo nobody there was able to > help me. I need your help with my WLAN on a Asus Eee PC 1000H. It has a > Ralink WiFi card > > --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > 01:00.0 Network controller [0280]: RaLink Device [1814:0781] > ********Subsystem: RaLink Device [1814:2790] > ********Flags: bus master, fast devsel, latency 0, IRQ 19 > ********Memory at fbef0000 (32-bit, non-prefetchable) [size=64K] > ********Capabilities: <access denied> > ********Kernel driver in use: rt2860 > ********Kernel modules: rt2860sta > --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > > I configured the rpmfusion repository and installed the rt2860 > package. There was a small caveat - I had to do "iwpriv ra0 radio_on" in > order to do anything related with WLAN, but afterward scanning was On my eeepc 901 (also using the ralink chipset) I had to do none of that. I installed the kmod package of the rt2860 driver (I've since learned that the akmod package may have been a better choice), and NM came up and I connected. as simple as that. > possible. But I can't connect my AP using Network Manager. Basically I > see those two lines in wpa_supplicant.log > > Trying to associate with 00:18:f3:85:6a:31 (SSID='memphis' freq=2437 MHz) > Authentication with 00:00:00:00:00:00 timed out. > > NM keeps asking me for a password, but my input is definitely correct. > > So I thought NM messes things up (as was my experience with my old > notebook) and I tried to get WLAN running using iwconfig + > wpa_supplicant configuration directly. Here is my wpa_supplicant.conf I > used. > > --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > > network={ > * * * * ssid="memphis" > * * * * scan_ssid=1 > * * * * psk="myverysecretpassword" > } > --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > > But it did not work either, the Eee PC still could not connect to the AP. > > The only way I can establish a WLAN connection is to compile the rt2860 > driver from the Ralink homepage > (http://www.ralinktech.com/ralink/Home/Support/Linux.html) without any > patches and configure it *only* for wpa_supplicant support, not NM > support! Then and only then I can connect to my AP using WPA *but* I > have to use iwpriv command to set the encryption password! (iwpriv set > WPA=secret) > > Did you succeed in using WLAN with F10 on Eee PC 1000H and if yes - how > did you do it? Do you have an idea how to convince Ralink's chip to > behave "normally"? > I've ran out of ideas what else to try. Do you see a point I'm obviously > missing? I've search the net, but it seems to work for everybody else, > contradicting my experience. Before I blew away the xandros-drived Linux that came on the 901 I had a lot of trouble getting wireless to work. One of the things I had to do to get it working is tweak a few settings on my wireless router. Have you tried (temporarily) relaxing some security features to see if you can get it going? There has also been some discussion of similar issues on the fedora forums. there's a topic on putting F10 on eeepc 901 and 1000 that has discussed a number of things, including wireless issues, that you may wish to check out. -- ---- Fred Smith -- fredex@fcshome.stoneham.ma.us ----------------------------- "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." ----------------------------- Jude 1:24,25 (niv) ----------------------------- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
Hi Adalbert,
I have two of these EeePC 1000h, and WPA2 is not supported by the default Linux OS installed, I installed Fedora 10 via PXE boot (using a network cable) slooowwww.. but it worked out of the box. I installed KDE only - which looks great cos the black theme matches the black version of this machine so well - oops getting off track. I then downloaded and compiled the 2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2 as per this thread: http://forums.fedoraforum.org/showthread.php?t=199434 (details you need at listed below). However, I'm using the newer version 1.8 (and there may be a newer one since, have not checked), I cannot remeber if it patched (sta_ioctl.patch) cleanly or not or even if you need the patch in the newer version, anyhow, reboot and it should work when you login. TIP: If you have a USB Stick (mine was 1GB) unzip and compile the drivers directly on that or better still, compile it on an NFS mount cos the SDD disk is really slow :( (this does not effect the everyday performance). Also, don't mess with wpa_supplicant and what not (i.e chkconfig etc) , just let NetworkManager do it's stuff. WPA2 works perfectly using this (and the network is very reliable). I also installed a PAM module that automatically logged on to the wireless when I log in (cos having to type in the Key Manager password every time I login was just plain annoying). (What would be nice is if it would connect via Wireless when in init 3 (like the cable) and use that connection for each user - and I think that's on the cards for NetworkManager in the future). INSTRUCTIONS FROM LINK ABOVE: 1. To be able to compile the driver we need a few extra packages. In the terminal (as root), type Code: yum install gcc kernel-devel kernel-headers 2. Obtain the latest Ralink driver here (1.7.0.0 at the time of writing this post) 3. Unzip the driver to a directory. 4. Open the directory, and go to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_main_dev.c 5. Look up "dev->nd_net" and replace it with "dev_net(dev)", then save the file and close it (thanx toCiaran McCreesh’s Blag for this tip). 6. Open 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/config.mk and change "HAS_WPA_SUPPLICANT" and "HAS_NATIVE_WPA_SUPPLICANT_SUPPORT" to "y". 7. Download hdp's patch, and copy it to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux 8. Open a terminal, cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux and type "patch sta_ioctl.c sta_ioctl.patch" 9. From the terminal cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0 and type "make", it should finish without any errors. 10. Type "make install", then when finished, exit the terminal. 11. If you restart the Eee PC and enable the wireless from the BIOS, it should be recognized without problems. Best of luck. Albert. Adalbert Prokop wrote: Hello! Last week I wrote to the fedora-laptop list, bo nobody there was able to help me. I need your help with my WLAN on a Asus Eee PC 1000H. It has a Ralink WiFi card --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 01:00.0 Network controller [0280]: RaLink Device [1814:0781] Subsystem: RaLink Device [1814:2790] Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at fbef0000 (32-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: rt2860 Kernel modules: rt2860sta --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- I configured the rpmfusion repository and installed the rt2860 package. There was a small caveat - I had to do "iwpriv ra0 radio_on" in order to do anything related with WLAN, but afterward scanning was possible. But I can't connect my AP using Network Manager. Basically I see those two lines in wpa_supplicant.log Trying to associate with 00:18:f3:85:6a:31 (SSID='memphis' freq=2437 MHz) Authentication with 00:00:00:00:00:00 timed out. NM keeps asking me for a password, but my input is definitely correct. So I thought NM messes things up (as was my experience with my old notebook) and I tried to get WLAN running using iwconfig + wpa_supplicant configuration directly. Here is my wpa_supplicant.conf I used. --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="memphis" scan_ssid=1 psk="myverysecretpassword" } --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- But it did not work either, the Eee PC still could not connect to the AP. The only way I can establish a WLAN connection is to compile the rt2860 driver from the Ralink homepage (http://www.ralinktech.com/ralink/Home/Support/Linux.html) without any patches and configure it *only* for wpa_supplicant support, not NM support! Then and only then I can connect to my AP using WPA *but* I have to use iwpriv command to set the encryption password! (iwpriv set WPA=secret) Did you succeed in using WLAN with F10 on Eee PC 1000H and if yes - how did you do it? Do you have an idea how to convince Ralink's chip to behave "normally"? I've ran out of ideas what else to try. Do you see a point I'm obviously missing? I've search the net, but it seems to work for everybody else, contradicting my experience. Any help is *very* appreciated. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
On Tue, Jan 13, 2009 at 05:12:14PM +0000, Albert Graham wrote:
> Hi Adalbert, > > I have two of these EeePC 1000h, and WPA2 is not supported by the > default Linux OS installed, Well, it certainly IS on a eeepc 901. Or would be if the default rt2860 drivers on the 901 linux worked. Many of us couldn't get it to work. Luckily "onlyconnect" on the eeepc forums had done a lot of the skull sweat and compiled drivers that did work. I have no idea if Asus has ever issued fixes for the wireless problem, as I've moved on to F10 on my eeepc. And there's no need to compile it for f10 either. Just add the RPM FUsion free and nonfree repositories then use "add/remove software" to add the kmod or akmod packages for the rt2860 driver. Voila. > > I installed Fedora 10 via PXE boot (using a network cable) slooowwww.. > but it worked out of the box. > > I installed KDE only - which looks great cos the black theme matches the > black version of this machine so well - oops getting off track. > > I then downloaded and compiled the > 2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2 as per this thread: > > http://forums.fedoraforum.org/showthread.php?t=199434 (details you need > at listed below). > > However, I'm using the newer version 1.8 (and there may be a newer one > since, have not checked), I cannot remeber if it patched > (sta_ioctl.patch) cleanly or not or even if you need the patch in the > newer version, anyhow, reboot and it should work when you login. > > TIP: If you have a USB Stick (mine was 1GB) unzip and compile the > drivers directly on that or better still, compile it on an NFS mount cos > the SDD disk is really slow :( (this does not effect the everyday > performance). > > Also, don't mess with wpa_supplicant and what not (i.e chkconfig etc) , > just let NetworkManager do it's stuff. > > WPA2 works perfectly using this (and the network is very reliable). > > I also installed a PAM module that automatically logged on to the > wireless when I log in (cos having to type in the Key Manager password > every time I login was just plain annoying). > > (What would be nice is if it would connect via Wireless when in init 3 > (like the cable) and use that connection for each user - and I think > that's on the cards for NetworkManager in the future). > > INSTRUCTIONS FROM LINK ABOVE: > > 1. To be able to compile the driver we need a few extra packages. In the > terminal (as root), type > Code: > > yum install gcc kernel-devel kernel-headers > > 2. Obtain the latest Ralink driver here (1.7.0.0 at the time of writing > this post) > 3. Unzip the driver to a directory. > 4. Open the directory, and go to > 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_main_dev.c > 5. Look up "dev->nd_net" and replace it with "dev_net(dev)", then save > the file and close it (thanx > toCiaran McCreesh’s Blag for this tip). > 6. Open 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/config.mk and > change "HAS_WPA_SUPPLICANT" and > "HAS_NATIVE_WPA_SUPPLICANT_SUPPORT" to "y". > 7. Download hdp's patch, and copy it to > 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux > 8. Open a terminal, cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux > and type "patch sta_ioctl.c > sta_ioctl.patch" > 9. From the terminal cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0 and type > "make", it should finish without > any errors. > 10. Type "make install", then when finished, exit the terminal. > 11. If you restart the Eee PC and enable the wireless from the BIOS, it > should be recognized without > problems. > > > Best of luck. > > Albert. > > > > > Adalbert Prokop wrote: > >Hello! > > > >Last week I wrote to the fedora-laptop list, bo nobody there was able to > >help me. I need your help with my WLAN on a Asus Eee PC 1000H. It has a > >Ralink WiFi card > > > >--- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > >01:00.0 Network controller [0280]: RaLink Device [1814:0781] > > Subsystem: RaLink Device [1814:2790] > > Flags: bus master, fast devsel, latency 0, IRQ 19 > > Memory at fbef0000 (32-bit, non-prefetchable) [size=64K] > > Capabilities: <access denied> > > Kernel driver in use: rt2860 > > Kernel modules: rt2860sta > >--- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > > > >I configured the rpmfusion repository and installed the rt2860 > >package. There was a small caveat - I had to do "iwpriv ra0 radio_on" in > >order to do anything related with WLAN, but afterward scanning was > >possible. But I can't connect my AP using Network Manager. Basically I > >see those two lines in wpa_supplicant.log > > > >Trying to associate with 00:18:f3:85:6a:31 (SSID='memphis' freq=2437 MHz) > >Authentication with 00:00:00:00:00:00 timed out. > > > >NM keeps asking me for a password, but my input is definitely correct. > > > >So I thought NM messes things up (as was my experience with my old > >notebook) and I tried to get WLAN running using iwconfig + > >wpa_supplicant configuration directly. Here is my wpa_supplicant.conf I > >used. > > > >--- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > >ctrl_interface=/var/run/wpa_supplicant > >ctrl_interface_group=wheel > > > >network={ > > ssid="memphis" > > scan_ssid=1 > > psk="myverysecretpassword" > >} > >--- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- > > > >But it did not work either, the Eee PC still could not connect to the AP. > > > >The only way I can establish a WLAN connection is to compile the rt2860 > >driver from the Ralink homepage > >(http://www.ralinktech.com/ralink/Home/Support/Linux.html) without any > >patches and configure it *only* for wpa_supplicant support, not NM > >support! Then and only then I can connect to my AP using WPA *but* I > >have to use iwpriv command to set the encryption password! (iwpriv set > >WPA=secret) > > > >Did you succeed in using WLAN with F10 on Eee PC 1000H and if yes - how > >did you do it? Do you have an idea how to convince Ralink's chip to > >behave "normally"? > >I've ran out of ideas what else to try. Do you see a point I'm obviously > >missing? I've search the net, but it seems to work for everybody else, > >contradicting my experience. > > > >Any help is *very* appreciated. > > > > > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- ---- Fred Smith -- fredex@fcshome.stoneham.ma.us ----------------------------- "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." ----------------------------- Jude 1:24,25 (niv) ----------------------------- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
fred smith schrieb:
Hello! > And there's no need to compile it for f10 either. Just add the > RPM FUsion free and nonfree repositories then use "add/remove software" > to add the kmod or akmod packages for the rt2860 driver. Voila. Well, my experience say otherwise... Voilà is not true. I just installed the akmod-rt2860 driver and restored the virgin wpa_supplicant.conf to please NM. But still no progress in this matter. >> http://forums.fedoraforum.org/showthread.php?t=199434 If this procedure does not succeed the next thing I will try is to backup F10 and restore the original WinXP. Then I'll connect to my AP and pull the battery. I suspect the Windows driver to leave the chipset in a dorment state. It's only a wild guess but I have no other idea. -- bye Adalbert -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
Adalbert Prokop wrote:
fred smith schrieb: Hello! And there's no need to compile it for f10 either. Just add the RPM FUsion free and nonfree repositories then use "add/remove software" to add the kmod or akmod packages for the rt2860 driver. Voila. Well, my experience say otherwise... Voilà is not true. I just installed the akmod-rt2860 driver and restored the virgin wpa_supplicant.conf to please NM. But still no progress in this matter. http://forums.fedoraforum.org/showthread.php?t=199434 If this procedure does not succeed the next thing I will try is to backup F10 and restore the original WinXP. Then I'll connect to my AP and pull the battery. I suspect the Windows driver to leave the chipset in a dorment state. It's only a wild guess but I have no other idea. Did FC10 possibly setup a driver for it before you installed the kmod driver ? If so that FC10 driver must be blacklisted in /etc/depmod.d/blacklist file or the kmod driver will conflict with the FC10 driver. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
Jim wrote on Friday 16 January 2009:
Hello! > Did FC10 possibly setup a driver for it before you installed the kmod > driver ? Which driver could F10 possibly setup? There is no rt2860sta module in the fedora flavored kernel and I suppose no other module is responsible for the ralink chipset id. Besides, basically my WLAN works - but the connection procedure is far from beeing comfortabale or even acceptable. The problems *seems* to lie not between the driver and the hardware, but between the driver and userland apps like wpa_supplicant and iwconfig. What I really would like to know is whether there is any hardware difference between the XP and Linux version of the Eee 1000H model... Or my Eee is just jinxed - it would be the most plausible explanation. ;) -- bye, Adalbert -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
Albert Graham schrieb:
First of all: thank all of you very much for your suggestions. As I should expect, none of us was completely right or wrong. ;) Here is what I found out. > Also, don't mess with wpa_supplicant and what not (i.e chkconfig etc) , > just let NetworkManager do it's stuff. That the point: NM would possibly do its stuff - if it could. But the great documentation and debugging abilities of NM make finding out what's going on a real challenge. So I rather stick to wpa_supplicant. NM uses it anyway. ;) To make a long story short: both WPA and WPA2 work fine but the key cipher is important. TKIP works, AES (CCMP) does *not*. Since my AP was broadcasting both of them wpa_supplicant chose AES and was stuck. Since I do not know how to tell NM to explicitly use TKIP I have to restrict my AP to TKIP or give up on NM and use wpa_supplicant directly. This is not a comforting decision, since WPA/TKIP has been cracked. http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9119 258&source=rss_news I would like you to confirm or to disprove my conclusion. Do you successfully use the Eee 1000H with WPA(2)+AES? Is it possible? -- bye Adalbert -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
Need help with WLAN on Eee PC 1000H
Adalbert Prokop schrieb:
> To make a long story short: both WPA and WPA2 work fine but the key > cipher is important. TKIP works, AES (CCMP) does *not*. Correction: CCMP does not work with both TKIP and CCMP enables. It works if TKIP is deactivated on the AP. Maybe only my FreeWRT on the router is fooling around. ;) -- bye Adalbert -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines |
| All times are GMT. The time now is 10:40 PM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.