Bug 224394 - wlan configuration does not work
Summary: wlan configuration does not work
Status: RESOLVED DUPLICATE of bug 224177
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Network (show other bugs)
Version: RC 1
Hardware: i686 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-29 06:56 UTC by Lars Olesen
Modified: 2006-11-29 13:32 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Olesen 2006-11-29 06:56:09 UTC
I have a wireless nic : Allnet 0271, which is supported by prism54, and yast detects it correctly. 
I have also downloaded the firmware for the card, and it is loaded. 
But if I set network (in yast configuration) to use ifup I can see that the config script for the interface is not found.
I then made a symlink called for instance ifcfg-eth2 to /etc/sysconfig/network/ifcfg-wlan...... , and then the network script successfully 
executes the script.
I can see (using iwevent) that the nic issues an associate request to the wireless router which is accepted, but dhcp does not work on the wireless interface. If I try to set route and ip manually for the interface I still don't get a connection. The wired ethernet port connects to the same router with no problems.

Note: I am not using knetworkmanager because I saw a bug report stating that there was a problem with knetworkmanager and prism54.
Also when I did try using knetworkmanager I coule see that the nic never associated eith the router.

I am using KDE.
Comment 1 Matej Horvath 2006-11-29 13:16:04 UTC
Please attach your yast log files (http://en.opensuse.org/Bugs/YaST), the /var/log/messages and output of the 'hwinfo --wlan'. 

Thank you
Comment 2 Matej Horvath 2006-11-29 13:32:41 UTC

*** This bug has been marked as a duplicate of bug 224177 ***