Bug 21042 - Stage 1: WEP not working (at least not for ipw2200)
Summary: Stage 1: WEP not working (at least not for ipw2200)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-07 20:52 CEST by Morgan Leijström
Modified: 2020-12-01 22:29 CET (History)
2 users (show)

See Also:
Source RPM: drakx-installer-binaries
CVE:
Status comment:


Attachments

Description Morgan Leijström 2017-06-07 20:52:18 CEST
Years ago I made Bug 9541 about WPA2 (and WPA) not working, and the status there is that it is not supported yet, but WEP is supposed to work.

So i make a new one here about *WEP* not working.

The system here works perfectly (and have for years) once installed.

I also, just for test, verified that installer works if i set no encryption at all, tested as fas as downloading stage 2 over that wifi.

Problem is that it do not work when i use WEP, as advertised.

__ Steps to Reproduce:

1. Router (D-Link DIR-868L): for this experiment i set the 2,4GHz interface to WEP 64 bit, key "12345" entered, bands b & g.

2. Test system: Thinkpad T43, Intel PRO/Wireless 2200BG Mini-PCI Adapter, driver ipw2200 works perfectly once mageia is installed - and have through all years :)

3. Boot network installer, nonfree version (i used cauldron i586 as of today)
e "Operation not supported".

4. I choose HTTP server, then NET device "wlp11s2 (ipw2200)"

5. Enter the key.

Dialog pops up: "unable to set WEP key "12345" on device "wlp11s2": Operation not supported.

The log at Alt-F3 show no error, but the lines:

* setting WEP key "TheHexaDecimalKey" on device "wlp11s2"
* unsetting automatic

So maybe the installer lack something needed for this specific card?

I can not see kernel messages; bug 21041.
Marja Van Waes 2017-06-07 22:11:44 CEST

CC: (none) => marja11
Assignee: bugsquad => mageiatools
Source RPM: (none) => drakx-installer-binaries

Comment 1 Martin Whitaker 2020-11-29 10:58:00 CET
"12345" is too short - you need to enter 10 hex digits.

If you are trying to use the ASCII equivalent of the key, I don't think the old stage 1 supported that. It *might* work with the latest cauldron netinstall if you include the quote marks - I'll have to try that.

CC: (none) => mageia

Comment 2 Martin Whitaker 2020-11-29 11:20:40 CET
And yes, with the latest cauldron netinstall, you can enter the ASCII equivalent by enclosing it in double quote marks.
Comment 3 Morgan Leijström 2020-11-29 11:29:17 CET
Great :)
I will try this and Bug 9541 and Bug 20141 in a couple days!
Comment 4 Morgan Leijström 2020-11-29 11:47:17 CET
typo 20141 -> bug 21041
Morgan Leijström 2020-11-30 01:03:08 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=9541

Comment 5 Morgan Leijström 2020-12-01 22:29:36 CET
Latest cauldron netinstall i586 on same system.

WEP connect OK using DHCP and both 10 and 26 hexadecimal char keys as well as 13 ASCII characters between double quotes.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.