Foro de elhacker.net

Bueno pues eso, tengo ese problema pero ahora dare unos datos.

Anteriormente tenia ese mismo problema, y lo solucione aplicando estos datos en una terminal:

wget http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2010-10-16.tar.bz2
tar -jxf compat-wireless-2010-10-16.tar.bz2
cd compat-wireless-2010-10-16
wget http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch
patch -p1 < mac80211.compat08082009.wl_frag+ack_v1.patch
wget http://patches.aircrack-ng.org/channel-negative-one-maxim.patch
patch ./net/wireless/chan.c channel-negative-one-maxim.patch
gedit scripts/update-initramfs
#*** FIND LINE 13: KLIB=/lib/modules/2.6.31-wl/build
#*** REPLACE WITH: KLIB=/lib/modules/$(uname -r)/build
make
sudo make install
sudo make unload
sudo reboot
------------------------------------------------------------------------------------------------

Pero formatie la PC e instale de nuevo linux y al tratar de descifrar mi propia clave WEP me topo con el mismo problema, a lo cual procedo a aplicar el metodo que anteriormente me lo habia solucionado. Pues bien lo aplico y me sorprendo al observar que esta ves no me lo soluciono :S
Debo aclarar ( si sirve de algo) que tengo el chipset: rtl8187

Tambien debo aclarar que antes de instalar aircrack actualize mi linux al 100% nose si eso tengo algo que ver ( creo anteriormente jamas actualize el SO)

ESpero me puedan ayudar se los agradeceria

En el foro hay varios temas sobre esto, sin embargo acá hay otra posible solución en la cual hay que cerrar algunos procesos que entran en conflicto con el canal.

"fixed channel" error message

If the top of your airodump screen looks something like:

 CH  6 ][ Elapsed: 28 s ][ 2008-09-21 10:39 ][ fixed channel ath0: 1
Then this means you started started airodump-ng with a fixed channel parameter (-c / –channel) but some other process is changing the channel. “CH 6” on the left is the channel that was specified when airodump-ng was started. “fixed channel ath0: 1” on the right indicates that ath0 was used when airodump-ng was started but the interface is currently on channel 1 (instead of channel 6). You might also see this channel number changing indicating that channel scanning is taking place.

It is critical that the root cause of the problem be eliminated and then airodump-ng restarted again. Here are some possible reasons and how to correct them:

There is one or more intefaces in “managed mode” and these are are scanning for an AP to connect to. Do not use any command, process or program to connect to APs at the same time as you use the aircrack-ng suite.
Other processes are changing the channel. A common problem are network managers. You can also use “airmon-ng check” on current versions of the aircrack-ng suite to identify problem processes. Then use “kill” or “killall” to destroy the problem processes. For example, use “killall NetworkManager && killall NetworkManagerDispatcher” to eliminate network managers.
If you are using the madwifi-ng driver and have more then the ath0 interface created, the driver may be automatically scanning on the other interfaces. To resolve this, stop all interfaces except ath0.
You have wpa_supplicant running at the same time. Stop wpa_supplicant.
You run airmon-ng to set the channel while airodump-ng is running. Do not do this.
You run another instance of airodump-ng in scanning mode or set to another channel. Stop airodump-ng and do not do this.
There is a known bug that affects recent versions of compat-wireless or wireless-testing drivers (shows channel as -1): http://trac.aircrack-ng.org/ticket/742

Muchas gracias amigo sinceramente. Pero ya lo solucione jajaja

nose que haya solucionado el problema pero lo que hize fue:

1.- Bajar los drivers de mi chipset de la pagina del fabricante: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=1&PFid=1&Level=6&Conn=5&DownTypeID=3&GetDown=false&Downloads=true#RTL8185L (recordar que tengo chipset rtl8187, sin contar que aprendi a compilar un programa e instalarlo en linux, cosa que no sabia)

2.- Aplicar supuestamente el parche: ( http://trac.aircrack-ng.org/attachment/ticket/742/0001-aireplay-ng-add-an-option-to-ignore-channel-1-error.patch )

Y digo supuestamente porque aplique esto: patch <nombre_del_archivo.patch (soy nuevo)

En fin solucionado  ;-) ;-)