WEP key setting doesn't work on IPW2200 without "restricted"

Bug #20247 reported by Martijn vdS on 2005-08-23
12
Affects Status Importance Assigned to Milestone
netcfg (Debian)
New
Unknown
netcfg (Ubuntu)
Medium
Unassigned

Bug Description

Setting the WEP-key on both my IPW2200s doesn't work unless I also set the
security mode to "restricted" manually on vc 2. This also works (but isn't
necessary) on my other wifi cards (prism54, atmel), so it should be safe to set
it always.

It can be done in two ways:

iwconfig eth0 key restricted your_wep_key_here

or in 2 steps:
iwconfig eth0 key your_wep_key_here
iwconfig eth0 key restricted

reassign 295801 netcfg
severity 295801 wishlist
thanks

Martijn vdS (martijn) wrote :

Setting the WEP-key on both my IPW2200s doesn't work unless I also set the
security mode to "restricted" manually on vc 2. This also works (but isn't
necessary) on my other wifi cards (prism54, atmel), so it should be safe to set
it always.

It can be done in two ways:

iwconfig eth0 key restricted your_wep_key_here

or in 2 steps:
iwconfig eth0 key your_wep_key_here
iwconfig eth0 key restricted

Jerome S. Gotangco (jsgotangco) wrote :

This workaround works for me in Colony 3.

Jerome S. Gotangco (jsgotangco) wrote :

(In reply to comment #1)
> This workaround works for me in Colony 3.

Also confirmed in Hoary with the Canonical-supplied Toshiba Tecra M2 laptop

Martijn vdS (martijn) wrote :

Really confirm it ;)

Note: This should also be changed in /etc/network/interfaces to be useful.

Martijn vdS (martijn) wrote :

In netcfg, wireless.c, line 241:

  wrq.u.data.flags = 0;

should probably be:

  wrq.u.data.flags = IW_ENCODE_RESTRICTED;

This is what wireless.18.h in wireless-tools source has to say about the matter:

/* Flags for encoding (along with the token) */
#define IW_ENCODE_INDEX 0x00FF /* Token index (if needed) */
#define IW_ENCODE_FLAGS 0xFF00 /* Flags defined below */
#define IW_ENCODE_MODE 0xF000 /* Modes defined below */
#define IW_ENCODE_DISABLED 0x8000 /* Encoding disabled */
#define IW_ENCODE_ENABLED 0x0000 /* Encoding enabled */
#define IW_ENCODE_RESTRICTED 0x4000 /* Refuse non-encoded packets */
#define IW_ENCODE_OPEN 0x2000 /* Accept non-encoded packets */
#define IW_ENCODE_NOKEY 0x0800 /* Key is write only, so not present */
#define IW_ENCODE_TEMP 0x0400 /* Temporary key */

Martijn vdS (martijn) wrote :

Also, prism54 "automatically" switches to Restricted mode when a WEP key is entered.

(why did I set this to assigned/accepted?)

Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: 17 Feb 2005 22:51:55 -0800
From: Philippe Troin <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: debian-installer: WEP "restricted" or "open" mode cannot be configured

Package: debian-installer
Version: rc2
Severity: normal

I need to run "iwconfig ethN enc restricted" to be able to access my
wireless access point. The Debian installer does not let me do that.

Phil.

Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Fri, 18 Feb 2005 19:12:46 +0100
From: Frans Pop <email address hidden>
To: <email address hidden>
Subject: Reassign #295801 to netcfg

reassign 295801 netcfg
severity 295801 wishlist
thanks

This still presists in Dapper Beta and previous Flight releases.

I will have to pull back my last comment: IPW2200 on a Canonical-sponsored Toshiba Tecra M2 now associates via WEP during setup and was able to download additional software as of Dapper Beta.

Jonathan Carter (jonathan) wrote :

Can this bug then be considered resolved then?

Wenzhuo Zhang (wenzhuo) wrote :

Confirming. The bug persists in 6.06.1 on ThinkPad X32. The workaround works well for me. However, I don't have to type the WEP key. ifup does that for me.

$ sudo eth1 key restricted

After typing the above command, the WiFi LED, which is below the LCD, lights up. Now I can bring up the wireless connection using either ifup or the Networking graphic tool.

The symtoms before manually switching the security mode to "restricted" can be found in the second post of <http://www.ubuntuforums.org/showthread.php?t=232349>.

Everything used to work well in breezy.

Wenzhuo Zhang (wenzhuo) wrote :

The command in my previous comment should read:

$ sudo iwconfig eth1 key restricted

Colin Watson (cjwatson) on 2007-04-19
Changed in netcfg:
assignee: kamion → nobody
status: Unconfirmed → Confirmed

Thank you for posting this bug.

Does this occur in Lucid?

Changed in netcfg (Ubuntu):
status: Confirmed → Incomplete

Closing because of no response.

Changed in netcfg (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.