Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24

Thread: Messed up wirless after using Aircrack

  1. #11
    Join Date
    Jan 2007
    Location
    Michigan, USA
    Beans
    1,184
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Messed up wirless after using Aircrack

    Quote Originally Posted by BeastMode View Post
    lo no wireless extensions.

    eth0 no wireless extensions.

    wmaster0 no wireless extensions.

    wlan0 IEEE 802.11bg ESSID:""
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Tx-Power=0 dBm
    Retry min limit:7 RTS thrff Fragment thr=2352 B
    Power Managementff
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    pan0 no wireless extensions.




    Flash cards are wonderful things.

    run

    Code:
    sudo iwconfig wlan0 txpower 100mw
    it will set the transmit to something other than 0, which should help you connect.

  2. #12
    Join Date
    Oct 2008
    Beans
    31

    Re: Messed up wirless after using Aircrack

    Quote Originally Posted by t4thfavor View Post
    run

    Code:
    sudo iwconfig wlan0 txpower 100mw
    it will set the transmit to something other than 0, which should help you connect.
    Need I reboot after this? Initially nothing is happening. Will reboot now.

    Upon reboot, still nothing.
    Last edited by BeastMode; July 29th, 2009 at 06:33 AM. Reason: Rebooted

  3. #13
    Join Date
    Jan 2007
    Location
    Michigan, USA
    Beans
    1,184
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Messed up wirless after using Aircrack

    Check the txpower after the reboot, it should say something like. It actually should say something like that after executing the command I gave you, but if not, a reboot is always good

    Code:
    wlan0     IEEE 802.11bg  ESSID:"NBIDavison"  
              Mode:Managed  Frequency:2.412 GHz  Access Point: 00:22:6B:8C:90:B6   
              Bit Rate=9 Mb/s   Tx-Power=20 dBm   
              Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
              Power Management:off
              Link Quality=39/100  Signal level:-67 dBm  Noise level=-92 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  4. #14
    Join Date
    Oct 2008
    Beans
    31

    Re: Messed up wirless after using Aircrack

    Quote Originally Posted by t4thfavor View Post
    Check the txpower after the reboot, it should say something like. It actually should say something like that after executing the command I gave you, but if not, a reboot is always good

    Code:
    wlan0     IEEE 802.11bg  ESSID:"NBIDavison"  
              Mode:Managed  Frequency:2.412 GHz  Access Point: 00:22:6B:8C:90:B6   
              Bit Rate=9 Mb/s   Tx-Power=20 dBm   
              Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
              Power Management:off
              Link Quality=39/100  Signal level:-67 dBm  Noise level=-92 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0


    After the reboot, it said 0. Now that I have run the command again (and haven't rebooted, yet) it does say the 20dbm.

  5. #15
    Join Date
    Oct 2008
    Beans
    31

    Re: Messed up wirless after using Aircrack

    I don't know if this helps, but before I started screwing with this thing, my wireless card was actually named ath0.

    I see no reference to that here now.

  6. #16
    Join Date
    Oct 2008
    Beans
    31

    Re: Messed up wirless after using Aircrack

    Huh.

    After the reboot, the txpower went back down to 0 again.

    Why would that be?

  7. #17
    Join Date
    Jan 2007
    Location
    Michigan, USA
    Beans
    1,184
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Messed up wirless after using Aircrack

    The driver changed. Madwifi uses athX ath5/9k uses wlanX.

    we need to find out what card you have.

    Code:
    sudo lshw
    youll see something like this.

    Code:
    -network:1
                    description: Wireless interface
                    product: AR2413 802.11bg NIC
                    vendor: Atheros Communications Inc.
                    physical id: 2
                    bus info: pci@0000:06:02.0
                    logical name: wmaster0
                    version: 01
                    serial: 00:19:7d:66:8d:80
                    width: 32 bits
                    clock: 33MHz
                    capabilities: pm bus_master cap_list logical ethernet physical wireless

  8. #18
    Join Date
    Oct 2008
    Beans
    31

    Re: Messed up wirless after using Aircrack

    Quote Originally Posted by t4thfavor View Post
    The driver changed. Madwifi uses athX ath5/9k uses wlanX.

    we need to find out what card you have.

    Code:
    sudo lshw
    youll see something like this.

    Code:
    -network:1
                    description: Wireless interface
                    product: AR2413 802.11bg NIC
                    vendor: Atheros Communications Inc.
                    physical id: 2
                    bus info: pci@0000:06:02.0
                    logical name: wmaster0
                    version: 01
                    serial: 00:19:7d:66:8d:80
                    width: 32 bits
                    clock: 33MHz
                    capabilities: pm bus_master cap_list logical ethernet physical wireless
    *-network DISABLED
    description: Wireless interface
    product: AR242x 802.11abg Wireless PCI Express Adapter
    vendor: Atheros Communications Inc.
    physical id: 0
    bus info: pci@0000:03:00.0
    logical name: wmaster0
    version: 01
    serial: 00:24:2c:0c:52:70
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress msix bus_master cap_list logical ethernet physical wireless
    configuration: broadcast=yes driver=ath5k_pci latency=0 module=ath5k multicast=yes wireless=IEEE 802.11bg



    Me thinks that whole "disabled" thingy is some sort of a problem.

  9. #19
    Join Date
    Jan 2007
    Location
    Michigan, USA
    Beans
    1,184
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Messed up wirless after using Aircrack

    More than likely, I found a thread here

    http://ubuntuforums.org/showthread.php?p=7695005

    Did you perhaps install any updates when aircracking? It appears a newer kernel broke some wireless chipsets recently. It appears yours is included.

    You can check your kernel version by typing uname -a into a console.


    Try to rmmod the ath5k driver, and then modprobe ath_pci

    Were going to unload the ath5k driver, and load the older one that makes ath0.
    Code:
    sudo rmmod ath5k
    sudo modprobe ath_pci
    Check if it works then, and if not folow the instuctibles on the link I sent.


    Its after 2AM here, Im going to bed, I will check back in the morning.
    Last edited by t4thfavor; July 29th, 2009 at 07:15 AM.

  10. #20
    Join Date
    Oct 2008
    Beans
    31

    Re: Messed up wirless after using Aircrack

    Quote Originally Posted by t4thfavor View Post
    More than likely, I found a thread here

    http://ubuntuforums.org/showthread.php?p=7695005

    Did you perhaps install any updates when aircracking? It appears a newer kernel broke some wireless chipsets recently. It appears yours is included.

    You can check your kernel version by typing uname -a into a console.


    Try to rmmod the ath5k driver, and then modprobe ath_pci

    Were going to unload the ath5k driver, and load the older one that makes ath0.
    Code:
    sudo rmmod ath5k
    sudo modprobe ath_pci
    Check if it works then, and if not folow the instuctibles on the link I sent.


    Its after 2AM here, Im going to bed, I will check back in the morning.
    I have to get near an actual ethernet port to try the fix in the link you provided, but the above code didn't work for me.

    I don't think this has anything to do with a kernel update. What I think has happened is that while I was messing around with WEP stuff, I disabled the Wireless device to enable monitoring...and now I don't know how to get it back...possibly.

    This post is more of a bump than anything else, however.

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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