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
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.
After the reboot, the txpower went back down to 0 again.
Why would that be?
The driver changed. Madwifi uses athX ath5/9k uses wlanX.
we need to find out what card you have.
youll see something like this.Code:sudo lshw
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
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
width: 64 bits
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.
More than likely, I found a thread here
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.
Check if it works then, and if not folow the instuctibles on the link I sent.Code:sudo rmmod ath5k sudo modprobe ath_pci
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.
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.