FedoraForum.org - Fedora Support Forums and Community
Results 1 to 13 of 13
  1. #1
    frow Guest

    Finds network, but can't seem to connect..

    Hey guys. I'm new to Linux so please understand me..

    I'm using Fedora 8 and have a bad computer for using it (HP dv-series).

    I've been fighting with the network-card for some days now (Broadcom 4311), but finally I got i too "work".

    It can find my network, but when it attempts to connect, it fails. Just going in loop with connecting and asking for password on the SSID.

    Since it can find my network, I can't see why it shouldn't be able to use it to.

    Get this from iwlist wlan0 scan

    Code:
    wlan0     Scan completed :
              Cell 01 - Address: 00:19:5B:07:21:DF
                        ESSID:"Sanden"
                        Mode:Master
                        Channel:6
                        Frequency:2.437 GHz (Channel 6)
                        Quality=65/100  Signal level=-63 dBm  Noise level=-56 dBm
                        Encryption key:on
                        Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                                  9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                                  48 Mb/s; 54 Mb/s
                        Extra:tsf=000000000af7056b
    So it finds my network..

    Any help please? And if you got some, please explain so I understand (but I'm not THAT noobish ;p)


    EDIT:

    dmesg | grep b43 (don't know what it is but i followed a guide) gave me this
    Code:
    b43-phy0: Broadcom 4311 WLAN found
    b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
    b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
    b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
    Registered led device: b43-phy0:tx
    Registered led device: b43-phy0:rx
    b43-phy0 debug: Chip initialized
    b43-phy0 debug: 32-bit DMA initialized
    b43-phy0 debug: Wireless interface started
    b43-phy0 debug: Adding Interface type 2
    b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: RX: Packet dropped
    b43-phy0 debug: RX: Packet dropped
    b43-phy0 debug: RX: Packet dropped
    b43-phy0 debug: RX: Packet dropped
    b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff
    b43-phy0 debug: RX: Packet dropped
    Packets dropping and disabling blablabla... what does it mean? Somethings wrong?
    Last edited by frow; 9th January 2008 at 07:31 PM.

  2. #2
    Join Date
    May 2007
    Posts
    99
    try using wicd manager for the wifi.

    btw how did you installed your card?

    -DB

  3. #3
    Join Date
    May 2007
    Posts
    99
    is it b43-fwcutter you have used to set up the wifi.

  4. #4
    frow Guest
    Hey. I tried the b43 (i read your thread Grub3r) but it didn't work. So I tried b43xx, and that was the one "working".

    How do I use wicd-manager? And where do I find it.

  5. #5
    Join Date
    May 2007
    Posts
    99

  6. #6
    frow Guest
    Hmm, didn't feel I got information there.

    Should I mention the encryption is WEP?

  7. #7
    Join Date
    May 2007
    Posts
    99
    Post #22:
    http://forums.fedoraforum.org/showth...t=wicd+service

    or you can set up interface manually by editing /etc/sysconfig/network-scripts/ifcfg-[interface]

    -db

  8. #8
    Join Date
    May 2007
    Posts
    99
    hmmm....

    the wep should be supported by network manager with no probs. just remember to have wpa_supplicant off at boot time.

    -db

  9. #9
    movitto Guest
    http://forums.fedoraforum.org/showthread.php?t=177798

    I am having the exact same problem. Wierd thing is, in Fedora 7 everything worked flawlessly (I even blogged about how to get everything running here (see step 11)). Problem is as soon as I upgraded to Fedora 8, I followed my instructions, and everything seemed to work (eg. I can see the wifi device and local networks) but as soon as I try to connect, I get nothing other than the spinning circles. I have no idea how to use any other wifi application (i tried wifi-radar but no networks showed up) and cannot manually set the network / device via a file in the filesystem (I move around alot, connecting to several networks).

    Nothing is fancy about my network setup. I have a linksys router, serving a WPA/TKIP/Preshared-Key network. On my local side, wpa_supplicant is running, and you can see alot of diagnosis output below.

    One thing to note, is I disabled IPV6 on my system as whenever I tried to connect my wifi card would be assigned an IPV6 address (I have no idea how, as I'm absolutely sure I have no IPV6 devices on my network) before exhibiting the aforementioned issue. The following is as much information as I could think to include, feel free to ask for more if it'll help.

    Code:
    uname -a
    Linux localhost.localdomain 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686 i386 GNU/Linux
    Code:
    lspci -vvv
    
    0c:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)
            Subsystem: Dell Unknown device 0007
            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
            Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
            Latency: 0, Cache Line Size: 64 bytes
            Interrupt: pin A routed to IRQ 17
            Region 0: Memory at f9ffc000 (32-bit, non-prefetchable) [size=16K]
            Capabilities: <access denied>
    Code:
    dmesg | grep wlan
    
    wlan0: ethernet device 00:1c:26:63:d8:d4 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4311.5.conf
    wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    Code:
    /sbin/ifconfig
    ...
    wlan0     Link encap:Ethernet  HWaddr 00:1C:26:63:D8:D4  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:39 errors:0 dropped:0 overruns:0 frame:0
              TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:4407 (4.3 KiB)  TX bytes:5282 (5.1 KiB)
              Interrupt:17 Memory:f9ffc000-fa000000
    Code:
    /sbin/iwlist wlan0 scanning
    
    wlan0     Scan completed :
              Cell 01 - Address: 00:40:10:10:00:03
                        ESSID:"GRIDNET"
                        Protocol:IEEE 802.11g
                        Mode:Managed
                        Frequency:2.412 GHz (Channel 1)
                        Quality:87/100  Signal level:-40 dBm  Noise level:-96 dBm
                        Encryption key:on
                        Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                                  24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                                  12 Mb/s; 48 Mb/s
                        Extra:bcn_int=100
                        Extra:atim=0
                        IE: WPA Version 1
                            Group Cipher : TKIP
                            Pairwise Ciphers (1) : TKIP
                            Authentication Suites (1) : PSK
              Cell 02 - Address: 00:0C:41:CA:27:ED
                        ESSID:"knrlinksys"
                        Protocol:IEEE 802.11b
                        Mode:Managed
                        Frequency:2.437 GHz (Channel 6)
                        Quality:7/100  Signal level:-91 dBm  Noise level:-96 dBm
                        Encryption key:on
                        Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                        Extra:bcn_int=100
                        Extra:atim=0
                        IE: WPA Version 1
                            Group Cipher : TKIP
                            Pairwise Ciphers (1) : TKIP
                            Authentication Suites (1) : PSK
    Code:
    cat /etc/modprobe.conf
    
    alias eth0 tg3
    alias scsi_hostadapter libata
    alias scsi_hostadapter1 ata_piix
    alias scsi_hostadapter2 usb-storage
    alias snd-card-0 snd-hda-intel
    options snd-card-0 index=0
    options snd-hda-intel index=0
    #alias wlan0 b43
    alias net-pf-10 off
    alias ipv6 off
    Code:
    cat /etc/modprobe.d/ndiswrapper 
    
    alias wlan0 ndiswrapper


    I downloaded an installed wlassistant as suggested, it starts up, I see my network, I configure it, but when I goto connect, I get the following:
    Code:
    ACTION: CONNECT.
    No DHCP client running.
    No pre-connection command specified.
    iwconfig_set: /sbin/iwconfig wlan0 mode managed channel 1 key off essid GRIDNET
    ==>stderr: Error for wireless request "Set Mode" (8B06) :
        SET failed on device wlan0 ; Operation not permitted.
    iwconfig_ap: /sbin/iwconfig wlan0 ap 00:40:10:10:00:03
    ==>stderr: Error for wireless request "Set AP Address" (8B14) :
        SET failed on device wlan0 ; Operation not permitted.
    ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
    Using wpa_supplicant driver: wext
    WPA client started. Waiting for status...
    ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
    CONNECTION FAILED.
    disconnect: /sbin/iwconfig wlan0 mode managed key off ap off essid off
    ==>stderr: Error for wireless request "Set Mode" (8B06) :
        SET failed on device wlan0 ; Operation not permitted.
    Code:
    sudo /usr/sbin/wpa_cli status
    Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
    From the last two blurbs it seems like not being able to connect to wpa_supplicant could be the problem. I tried googling it, and found others in the same situation, but unfortunately no answer. One very very important thing to note is connecting to an unsecured network works flawlessly!!!! So obviously the problem is something w/ wpa_supplicant

    Code:
    cat /etc/wpa_supplicant/wpa_supplicant.conf
    
    ctrl_interface=/var/run/wpa_supplicant
    ctrl_interface_group=wheel
    I am really lost on this one (I have had wireless woes before but never the situation where I am able to see networks but not connection) so any help will be appreciated. Thanks alot!
    Last edited by movitto; 12th January 2008 at 10:21 PM.

  10. #10
    movitto Guest
    additional output (last post was too long to include it)

    Code:
    tail -f /var/log/messages      (when attempting w/ Networkmanager)
    
    Jan 12 16:22:49 localhost NetworkManager: <info>  User request for activation of wlan0.
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activating device wlan0
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0/wireless): access point 'Auto GRIDNET' has security, but secrets are required.
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Jan 12 16:22:49 localhost NetworkManager: Missing or invalid key management
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0/wireless): connection 'Auto GRIDNET' has security, and secrets exist.  No new secrets needed.
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: added 'ssid' value 'GRIDNET'
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: added 'psk' value '<omitted>'
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: added 'proto' value 'WPA RSN'
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: added 'pairwise' value 'TKIP CCMP'
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: added 'group' value 'WEP40 WEP104 TKIP CCMP'
    Jan 12 16:22:49 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Jan 12 16:22:49 localhost NetworkManager: <info>  Config: set interface ap_scan to 1
    Jan 12 16:22:49 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 0 -> 2
    Jan 12 16:22:52 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 2 -> 3
    Jan 12 16:22:52 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 3 -> 4
    Jan 12 16:22:52 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 4 -> 5
    Jan 12 16:22:52 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 5 -> 6
    Jan 12 16:22:56 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 6 -> 4
    Jan 12 16:22:56 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 4 -> 5
    Jan 12 16:22:56 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 5 -> 6
    Jan 12 16:23:01 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 6 -> 4
    Jan 12 16:23:01 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 4 -> 5
    Jan 12 16:23:01 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 5 -> 6
    Jan 12 16:23:05 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 6 -> 4
    Jan 12 16:23:06 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 4 -> 5
    Jan 12 16:23:06 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 5 -> 6
    Jan 12 16:23:11 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 6 -> 4
    Jan 12 16:23:11 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 4 -> 5
    Jan 12 16:23:11 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 5 -> 6
    Jan 12 16:23:14 localhost NetworkManager: <info>  Activation (wlan0/wireless): association took too long, asking for new key.
    Jan 12 16:23:14 localhost NetworkManager: <info>  (wlan0) Supplicant interface state change: 6 -> 0
    Jan 12 16:23:26 localhost NetworkManager: <info>  wlan0: link timed out.
    Jan 12 16:23:27 localhost NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: applet.c.3251 (get_secrets_dialog_response_cb): canceled.
    Jan 12 16:23:27 localhost NetworkManager: <info>  Activation (wlan0) failed for access point (GRIDNET)
    Jan 12 16:23:27 localhost NetworkManager: <info>  Marking connection 'Auto GRIDNET' invalid.
    Jan 12 16:23:27 localhost NetworkManager: <info>  Activation (wlan0) failed.
    Jan 12 16:23:27 localhost NetworkManager: <info>  Deactivating device wlan0.
    Code:
    tail -f /var/log/wpa_supplicant.log
    
    Trying to associate with 00:40:10:10:00:03 (SSID='GRIDNET' freq=2412 MHz)
    WPA: EAPOL-Key Replay Counter did not increase - dropping packet
    Associated with 00:40:10:10:00:03
    Associated with 00:40:10:10:00:03
    Associated with 00:40:10:10:00:03
    Associated with 00:40:10:10:00:03
    Associated with 00:40:10:10:00:03
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Authentication with 00:00:00:00:00:00 timed out.
    Last edited by movitto; 12th January 2008 at 10:40 PM.

  11. #11
    movitto Guest
    Big revelation as I continue to play around w/ this. If I first connect to an unencrypted network, it succeeds, after which if I try to connect to my encrypted network it works. One thing to note though, the original network i connect to is just my network with wireless encryption disabled. So I'm not sure if the 2nd success is a result of some router-specific data being transmitted during the unencrypted session and used in the encrypted one. Regardless, its still not an optimal solution as I am not always able to guarantee that there will be an unencrypted network near by. Gonna keep on hacking at it

  12. #12
    Join Date
    Dec 2004
    Location
    IL, USA
    Age
    43
    Posts
    72

    Exact same problem

    I am having the same problem on my system. Have you found a work around yet? I know that wpa_supplicant has to be the issue.

  13. #13
    adking80 Guest

    Same problem for me too.

    (i tried wifi-radar but no networks showed up)
    Try editing /etc/wifi-radar/wifi-radar.conf and changing the interface from eth1 to wlan0. I had that problem. If you run wifi-radar in a terminal as root you should get a little more info on your problem.

    But wifi-radar doesn't work well for me; NetworkManager just stopped working recently. Weird.

Similar Threads

  1. Can't Connect to a wireless network with Network Manager
    By cirne in forum Servers & Networking
    Replies: 23
    Last Post: 2nd August 2008, 10:43 AM
  2. Using Network Manager to connect FC6 to wireless network.
    By DalekClock in forum Servers & Networking
    Replies: 8
    Last Post: 24th March 2007, 11:56 PM
  3. Apt-Get finds Problems that Yum Doesnt?
    By Raafi in forum Using Fedora
    Replies: 3
    Last Post: 3rd April 2006, 02:54 AM
  4. rkhunter finds some bad binaries
    By jim in forum Servers & Networking
    Replies: 3
    Last Post: 25th September 2005, 03:01 PM
  5. NetworkManager finds the wireless network but cannot connect
    By kwarrior in forum Hardware & Laptops
    Replies: 12
    Last Post: 4th May 2005, 08:31 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •