Bug 139660 - can't set channel in ad-hoc mode if essid is empty
Summary: can't set channel in ad-hoc mode if essid is empty
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-17 09:55 UTC by Crystal Xiong
Modified: 2015-01-04 22:12 UTC (History)
1 user (show)

Fixed In Version: RHEL40-Pre-RC2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-12-27 10:21:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Crystal Xiong 2004-11-17 09:55:39 UTC 
Description of problem:

Can't set channel if essid is empty in ad-hoc mode.

Version-Release number of selected component (if applicable):
ipw2100 v0.56

How reproducible:
Every time.

Steps to Reproduce:
1. % iwconfig eth1 mode Ad-hoc channel 4
   # can't set channel.

2. % modprobe -r ipw2100; modprobe ipw2100 mode=1 channel=4
  # failed to set channel

3. iwconfig eth1 mode ad-hoc essid "abc" channel 4
  # channel was set correctly.

  
Actual results:


Expected results:


Additional info:
Comment 1 Crystal Xiong 2004-12-27 10:21:29 UTC 
Did this test again on RHEL40-Pre-RC2. Now the 1.0.0 2100 driver can 
set channel successfully in ad-hoc mode even if essid is empty.
So this bug seems to have been fixed.
Note You need to log in before you can comment on or make changes to this bug.