LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 07-17-2006, 06:05 PM   #1
pwalden
Member
 
Registered: Jun 2003
Location: Washington
Distribution: Fedora FC19, Raspbian
Posts: 274

Rep: Reputation: 36
NetworkManager and MadWiFi no go


I have 2.6.17-1.2157_FC5 and kmod-madwifi-0.9.0-1.2.6.17.2157_FC5 from livna. I think the answer to getting madwifi working with NetworkManager on FC5 is fugetaboutit.

Basically, NetworkManager sees my ath0 card and successfully scans nearby networks. When I select one, regardless of how open or security keyed it is, I cannot get an IP from the network's DHCP server.

I can successfully connect using system-configuration-network. Yes, I have completely removed the network-configuration setup to ensure it was not interferring with NetworkManager. [on the side, I had the *dreaded card not showing up the wireless wizard* problem while trying to get it back. I hand entered the ifcng-ath0 and keys-ath0 device files to get around it]

I can left mouse click on the NetworkManager applet and see the list of nearby network with their relative signal strengths. I select mine. The dialog asking for the key comes up and I enter it, the same one that works with system-configuration-network. It then takes awhile to show a no-connect on the applet. If I plug in the ethernet cable, the manager automatically connects to it.

Poking around fedoraforums and the madwifi wiki, all you find is shared ignorance of the problem.

My system log seems to point towards NetworkManager mis-handling the dhcp client.


Thoughts?

Here is the system log of the failed attempt(s):

Quote:
Jul 17 11:41:55 walden5 NetworkManager: <information> starting...
Jul 17 11:41:55 walden5 NetworkManager: <information> ath0: Device is fully-supported using driver 'ath_pci'.
Jul 17 11:41:55 walden5 NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start
Jul 17 11:41:55 walden5 NetworkManager: <information> nm_device_init(): device's worker thread started, continuing.
Jul 17 11:41:55 walden5 NetworkManager: <information> Now managing wireless (802.11) device 'ath0'.
Jul 17 11:41:55 walden5 NetworkManager: <information> Deactivating device ath0.
Jul 17 11:41:57 walden5 NetworkManager: <information> eth0: Device is fully-supported using driver '3c59x'.
Jul 17 11:41:57 walden5 NetworkManager: <information> nm_device_init(): waiting for device's worker thread to start
Jul 17 11:41:57 walden5 NetworkManager: <information> nm_device_init(): device's worker thread started, continuing.
Jul 17 11:41:57 walden5 NetworkManager: <information> Now managing wired Ethernet (802.3) device 'eth0'.
Jul 17 11:41:57 walden5 NetworkManager: <information> Deactivating device eth0.
Jul 17 11:41:57 walden5 NetworkManager: <information> Updating allowed wireless network lists.
Jul 17 11:41:57 walden5 NetworkManager: <WARNING> nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
Jul 17 11:42:04 walden5 NetworkManager: <information> User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / WaldenPond
Jul 17 11:42:04 walden5 NetworkManager: <information> Deactivating device ath0.
Jul 17 11:42:06 walden5 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Jul 17 11:42:06 walden5 NetworkManager: <information> Device ath0 activation scheduled...
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) started...
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0/wireless): access point 'WaldenPond' is encrypted, but NO valid key exists. New key needed.
Jul 17 11:42:06 walden5 NetworkManager: <information> Activation (ath0) New wireless user key requested for network 'WaldenPond'.
Jul 17 11:42:07 walden5 NetworkManager: <information> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0) New wireless user key for network 'WaldenPond' received.
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
Jul 17 11:42:30 walden5 NetworkManager: <information> Activation (ath0/wireless): access point 'WaldenPond' is encrypted, and a key exists. No new key needed.
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'INTERFACE_ADD ath0 madwifi /var/run/wpa_supplicant '
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'AP_SCAN 1'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'ADD_NETWORK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was '0'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 ssid 57616c64656e506f6e64'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: sending command 'ENABLE_NETWORK 0'
Jul 17 11:42:31 walden5 NetworkManager: <information> SUP: response was 'OK'
Jul 17 11:42:31 walden5 NetworkManager: <information> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Jul 17 11:42:51 walden5 NetworkManager: <information> Activation (ath0/wireless): association took too long (>20s), failing activation.
Jul 17 11:42:51 walden5 NetworkManager: <information> Activation (ath0) failure scheduled...
Jul 17 11:42:51 walden5 NetworkManager: <information> Activation (ath0) failed for access point (WaldenPond)
Jul 17 11:42:51 walden5 NetworkManager: <information> Activation (ath0) failed.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Madwifi-old + Aircrack/Trouble compiling madwifi Ashex Linux - Software 7 04-05-2006 11:39 PM
Madwifi-old + Aircrack/Trouble compiling madwifi Ashex Linux - Software 0 03-05-2006 06:55 PM
Besides NetworkManager, shreks Fedora 1 01-18-2006 02:26 AM
NetworkManager baparekh Linux - Networking 1 07-28-2005 04:05 AM


All times are GMT -5. The time now is 11:29 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration