Bug 213297 - Setting wifi Mode to "Auto", the Channel is forced and I have to enter it manually!
Summary: Setting wifi Mode to "Auto", the Channel is forced and I have to enter it man...
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-31 18:18 UTC by Ahmed Kamal
Modified: 2009-07-14 18:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 18:27:53 UTC
Type: ---

Attachments (Terms of Use)

Description Ahmed Kamal 2006-10-31 18:18:01 UTC
Description of problem:
When I use system-config-network tool to set the settings for my ipw2200 Wifi
card, I use Mode=Auto, The "Channel" field is enabled, and the number in the
box, is saved to file. That is, I must specify the correct channel number! By
default it was channel=1, so my wifi could not connect at all. When I delete the
channel=1 line from ifcfg-eth0, then perform system-config-network restart, the
wifi card connected correctly

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

How reproducible:
100% reproducible

Steps to Reproduce:
1. Login as root, open system-config-network
2. Double click on the wifi interface, choose "Wireless settings" tab, choose
3. Click "OK" save & exit. The CHANNEL=1 field is saved to ifcfg-eth0
4. WiFi will not connect unless the Access Point is working on channel 1 by
Actual results:
CHANNEL=1 is saved to file, forcing the channel

Expected results:
The CHANNEL line should not be written to file at all

Additional info:
I marked priority as high, since this in effect breaks WiFi for all people
unless they know their channel number!

Comment 1 George Steinmetz 2007-06-24 03:52:01 UTC
I've confirmed this bug in system-config-network 1.3.96:  I worked around it by
changing the CHANNEL=1 line to CHANNEL=0, but since system-config-network only
allows channels 1-14, it replaces 0 with 1 whenever it is run.

Comment 2 Bug Zapper 2008-04-04 04:18:24 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 3 Jiri Moskovcak 2008-04-23 13:08:03 UTC
I've added option "auto" to channel selector, so it's not forced anymore. 
Should be in next update.


Comment 4 John Poelstra 2008-05-05 23:07:45 UTC
per last comment assuming "next update" refers to rawhide.  changing version and
placing in modified

Comment 5 Bug Zapper 2008-05-14 02:26:40 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 6 Bug Zapper 2009-06-09 22:19:43 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 7 Bug Zapper 2009-07-14 18:27:53 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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