Bug 223665 - ESSID set via iwconfig is shortened by the last character
Summary: ESSID set via iwconfig is shortened by the last character
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
(Show other bugs)
Version: 6
Hardware: i686 Linux
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-21 16:28 UTC by Jan Schäfer
Modified: 2018-04-11 12:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-31 17:28:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jan Schäfer 2007-01-21 16:28:42 UTC
Description of problem: ESSID set via iwconfig is shortened by the last character

Version-Release number of selected component (if applicable):

How reproducible: Try to set the ESSID on the console or via system-config-network

Steps to Reproduce:
1. iwconfig wlan0 essid "Name of your Network"
1. put in the network name in the configuration dialog and change foreward to
the next dialog and then back
Actual results:
The ESSID is shortened by one character
"MyNetwork" becomes "MyNetwor"

Expected results:
The ESSID is not shortended

Additional info:
A workaround is to put in an additional character
"MyNetworkX" becomes the right "MyNetwork" and everthing works.

Comment 1 Matěj Cepl 2007-01-29 17:28:07 UTC
Cannot reproduce with this package (but I don't have space in ESSID and using

Comment 2 Christopher Aillon 2007-01-29 22:18:40 UTC
I think this is actually a kernel problem.  Is this using the rt2x00 drivers? 
Does reverting to an older kernel, such as kernel-2.6.18-1.2869.fc6 fix the problem?

Comment 3 Jan Schäfer 2007-01-30 06:59:54 UTC
@Matej: I don't have a space in my ESSID either.

@Christopher: Yes I'm using the rt2x00 drivers. The problem occured after the
last kernel update.

Comment 4 Christopher Aillon 2007-01-30 18:16:40 UTC
Okay, over to kernel.

Comment 5 John W. Linville 2007-01-30 19:17:28 UTC
Where are you getting the rt2x00 drivers?

There was an upstream change to the internal wireless extensions API.  Some 
drivers had to be modified as a result.  Since the rt2x00 drivers are outside 
the kernel, their maintainers will need to make the appropriate changes.

Comment 6 Jan Schäfer 2007-01-30 21:47:37 UTC
I used the lastest BETA rt2500 driver (v1.1.0-b4) for the RT2500 chip set as
listed on the project site:


I'll try the nightly CVS tarball for the old rt2500 and also for the new rt2x00

Comment 7 Jan Schäfer 2007-01-30 22:18:34 UTC
The nightly CVS tarballs 


are working correcty for me now. Thanks for pushing me in the right direction.
I'll file a bug report in the rt2x00 project now.

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