|
Bugzilla – Full Text Bug Listing |
| Summary: | During installation using WIFI WEP encryption shared key is not set | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Steen Bank Johnsen <sbj> |
| Component: | YaST2 | Assignee: | Helmut Schaa <hschaa> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | coolo |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
YaST2 log
YaST2 log YaST2 log YaST2 log NetworkManager log messages |
||
|
Description
Steen Bank Johnsen
2007-09-20 15:58:51 UTC
you're talking about linuxrc or network setup during yast? Because the later is not supposed to setup WIFI When installation detects network cards it tells you that the WIFI interface isn't encrypted. You have the opportunity to change that. So I did choose to change the interface and did setup WEP encryption. Later the installation ask if You want to do an network test and that one failed. The only thing missing from the interface was to change from open to restricted with iwconfig. The key itself was correctly setup as was the ESSID. I think this is a dup then *** This bug has been marked as a duplicate of bug 308763 *** ok, most likely not a dup please attach your yast logs then Created attachment 173940 [details]
YaST2 log
Created attachment 173941 [details]
YaST2 log
Created attachment 173942 [details]
YaST2 log
Created attachment 173943 [details]
YaST2 log
Created attachment 173951 [details]
NetworkManager log
Created attachment 173952 [details]
messages
I assume this is something for you Do you use NetworkManager or traditional method for network setup? I don't recall to have used other than default. So if thats NetworkManager or traditional I don't know. Michal, could you please have a look at this bug? Do you think this issue is still present in 11.0? Fixed in 11.0. Nevertheless thanks for reporting. |