Bug 485189 - Can't connect to an Ad Hoc network
Can't connect to an Ad Hoc network
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-12 02:42 EST by Juhani Jaakola
Modified: 2009-12-18 02:54 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:54:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Excerpt from /var/log/messages during a failed connect (2.66 KB, text/plain)
2009-02-12 02:42 EST, Juhani Jaakola
no flags Details

  None (edit)
Description Juhani Jaakola 2009-02-12 02:42:32 EST
Created attachment 331663 [details]
Excerpt from /var/log/messages during a failed connect

Description of problem:
I created an Ad Hoc network using NetworkManager to share my 3G connection. I can connect to that network from an Acer laptop when I run Windows XP Home Edition, Version 2002, SP3. But I can't connect to the same network when I boot the same laptop to Fedora 10.

See the attached excerpt from /var/log/message from the Acer laptop. The laptop has an Atheros-based WLAN card:

--- begin of quote from /var/log/messages ---
ath_hal: module license 'Proprietary' taints kernel.
ath_pci 0000:04:05.0: PCI INT A -> Link[LNK2] -> GSI 19 (level, high) -> IRQ 19
MadWifi: ath_attach: Switching rfkill capability off.
wifi0: Atheros AR2413 chip found (MAC 7.8, PHY 2112A 4.5, Radio 5.6)
ath_pci: wifi0: Atheros 2413: mem=0xc3000000, irq=19
--- end of quote ---

# lspci -v
04:05.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
	Subsystem: AMBIT Microsystem Corp. Device 0418
	Flags: bus master, medium devsel, latency 96, IRQ 19
	Memory at c3000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
	Kernel driver in use: ath_pci
	Kernel modules: ath5k, ath_pci

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

How reproducible:

Steps to Reproduce:
1. Select the Ad Hoc network from NetworkManager
Actual results:
No connection

Expected results:
Connection established

Additional info:
Comment 1 Bug Zapper 2009-11-18 06:05:49 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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 2 Bug Zapper 2009-12-18 02:54:12 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.