Bug 133500
| Summary: | wireless device configuration does not allow changes to channel or transmit rate | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jason 'vanRijn' Kasper <vr> |
| Component: | system-config-network | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | arequipeno, mattdm, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-07 00:00:51 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 87718 | ||
|
Description
Jason 'vanRijn' Kasper
2004-09-24 14:21:48 UTC
If you change the "Mode" to "Auto" or "Ad-Hoc", you can specify the channel and the transmit rate... Why do you need to set this in "Managed" mode????? well, I'll be darned. lol. I must have wasted a good day at least
trying to work around this. Had I only known that using "Auto"
instead of "Managed" would let me do this... it would have saved me
lots of time. =:/
This is from the iwconfig man page:
mode Set the operating mode of the device, which depends on
the net-
work topology. The mode can be Ad-Hoc (network composed
of only
one cell and without Access Point), Managed (node
connects to a
network composed of many Access Points, with
roaming), Master
(the node is the synchronisation master or acts as an
Access
Point), Repeater (the node forwards packets between
other wire-
less nodes), Secondary (the node acts as a
backup mas-
ter/repeater), Monitor (the node acts as a passive
monitor and
only receives packets) or Auto.
Example :
iwconfig eth0 mode Managed
iwconfig eth0 mode Ad-Hoc
The topology that I'm in best fits the description of "Managed",
namely "node connects to a network composed of many Access Points,
with roaming". This is why I chose "Managed", and in fact, have used
Managed for quite a while with success in debian before I started
using fedora, when I iwconfig'd my card manually.
Is there a reason that transmit rate and channel should not be changed
when a card is in a managed topology? The user should still be
allowed to change these things, shouldn't he?
this is still a problem, and now is causing a problem with NetworkManager, I believe, since NetworkManager only works for me if mode is set to Managed, which as noted above, isn't configurable for me via the GUI. Is this being looked at anymore? In managed mode, the card itsself searches for the ESSID on every channel, so I thought this is not necessary.. Well, according to the iwconfig man page I quoted above, it sounds like a the very least, it would be the correct thing to do, I thought. And, I can say with certainty that unless I'm able to configure the channel and rate via the GUI config tool, my wireless card does not work. Thanks Harald!! Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp |