Ubuntu-fr

systemex2

Aircrack-ng

salut a tout
j'ai installé aircrack mais quand je lance la commande airmon-ng ça me donne :

Interface    Chipset        Driver

eth1        Unknown         wl

et pour airmon-ng start eth1 ça donne :

Found 5 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID    Name
1015    avahi-daemon
1016    avahi-daemon
1017    NetworkManager
1060    wpa_supplicant
10793    dhclient
Process with PID 10793 (dhclient) is running on interface eth1


Interface    Chipset        Driver

eth1        Unknown         wl (monitor mode enabled)

la question : c'est quoi l'attribut que je dois donner à airodump-ng?
normallement sous BackTrack sous l'interface wlan0 la commande est airodump-ng mon0

jacobus77

Re : Aircrack-ng

Visiblement ton interface n'est pas wlan0 mais eth1 et ton interface moniteur n'est pas mon0 mais eth1, ça marchera  si ta carte et tes drivers sont compatibles avec le mode moniteur.

systemex2

Re : Aircrack-ng

voila ce que me donne airodump-ng :

ioctl(SIOCSIWMODE) failed: Invalid argument

ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead.  Make
sure RFMON is enabled: run 'airmon-ng start eth1 <#>'
Sysfs injection support was not found either.

jacobus77

Re : Aircrack-ng

A priori ta carte, ton firmware ou tes drivers ne supportent pas le mode monitor. Pour vérifier, muni toi de ton modèle de carte (via lspci) et va faire un tour sur le forum d'aircrack-ng.

systemex2

Re : Aircrack-ng

la reponse de Ispci est :

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400M GS] (rev a1)
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
09:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
09:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
09:09.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
09:09.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)

jacobus77

Re : Aircrack-ng

Tu devrais peut etre chercher sur le forum...

http://www.google.fr/search?hl=fr&q=BCM … ntu-fr.org

systemex2

Re : Aircrack-ng

Merci beaucoup le problème était dans le pilote STA que j'utilisais à la place du BCM43
c'est réglé