|
Bugzilla – Full Text Bug Listing |
| Summary: | Unable to connect using WPA-TKIP with RaLink RT2500 card | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Rick Centeno <rick.centeno> |
| Component: | Network | Assignee: | Joachim Gleissner <joachim.gleissner> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | mvidner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
my efcfg-wlan-ra0
the dmesg output /var/log/messages |
||
Created attachment 61069 [details]
my efcfg-wlan-ra0
Created attachment 61070 [details]
the dmesg output
Created attachment 61071 [details]
/var/log/messages
Assign to yast2-network due missing configuration point for this problem. Add maintainer of wireless-tools to CC. Joachim please have a look and tell me if yast needs improvement. WPA with Ralink devices is not supported yet on SUSE Linux. As the driver wasn't included in SL 9.2 you probably compiled the driver yourself and used the RaConfig tool for setting up WPA. The Ralink driver is actually rewritten and will most probably work with wpa_supplicant as soon WPA is implemented. So there is no need to modify YaST. Joachim, Does this mean that there is no way to use Suse 10 with this set-up for the time being? Do I need to go back to 9.2 or 9.3? There the RT2500 driver worked AFAIK w/o wpa_supplicant support, after compiling it myself Grateful for your comments and guidance on way forward/timing. > Does this mean that there is no way to use Suse 10 with this set-up for the time being? Yes, exactly. > There the RT2500 driver worked AFAIK w/o wpa_supplicant support, after compiling it myself No one stops you from doing that also on 10.0. In fact, you only need to compile and install the RaConfig tool. And how about 10.1? Why don't we package RaConfig? Because we're going to include the new driver in 10.1 which obsoletes RaConfig. I don't know whether it will have already WPA support, though. |
After upgrading (reinstalling) from 9.2 to 10.0 the RaLink network card was not longer able to connect to my home network which is requiring WPA-TKIP configuration. Configuring YAST the card did not solve the issue, as Yast does not let you specify TKIP. Under 9.2 the WPA_supplicant was not required for the RT2500 module. NOw it is being called as I can see from the trace, but is unable to make a connection nor getting an ip address. Making an open connection to a non- secured basestation (the neighbours' one) is achievable, but not wanted. ifup-ra0: linux:~ # ifup ra0 ra0 device: RaLink Ralink RT2500 802.11 Cardbus Reference Card (rev 01) ra0 configuration: wlan-ra0 ra0 warning: WPA configured but may be unsupported ra0 warning: by this device ra0 starting wpa_supplicant WEXT auth param 7 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported Starting DHCP Client Daemon on ra0... . . . . . no IP address yet... backgrounding. Doing iwconfig show the connection to an external basestation: iwconfig: ra0 RT2500 Wireless ESSID:"SpeedTouchE02738" Mode:Managed Frequency=2.412 GHz Bit Rate:11 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality=0/100 Signal level=-101 dBm Noise level:-216 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0