Author Topic: WEP Key, Airmon-ng - problems?  (Read 13379 times)

aronk

  • Newbie
  • *
  • Posts: 5
    • View Profile
on: May 24, 2013, 11:50:10 AM
I have been an user of ubuntu for long time, I like the idea of open source, but 9 months ago I decided to learn more about
advanced options that this distribution gives to users. So I've chosen to try to break simple wireless networks, especially
with WEP key protection.

Then I come to the first wall, I have been searching a lot of tutorials (youtube, forums, blogs, sites), nothing worked for me.
Someone told me: "You should use backtrack, it's best for that", i tried backtrack 3, didn't work, then tried backtrack 4 (didn't work too)

And now I'm using Backbox (I hope that it will be successful), so now I have few questions:

1. After I type airmon-ng, the answer is this:

Interface   Chipset      Driver

eth1      Unknown    wl - [phy0]



- Why is Chipset unknown, and where is wlan0, what to do to fix this?

2. When I type this: airmon-ng start eth1 (or wlan0), the answer is:

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
1024   NetworkManager
1027   avahi-daemon
1028   avahi-daemon
1111   wpa_supplicant
2781   dhclient
Process with PID 2781 (dhclient) is running on interface eth1


Interface   Chipset      Driver

eth1      Unknown    wl - [phy0]mon0: ERROR while getting interface flags: No such device

            (monitor mode enabled on mon0)

 ---How to kill some of these?
______________________________________________________________
 
 I will put here additional informations about my hardware (may be helpful)
 
 
1. *-network
                description: Wireless interface
                product: BCM4313 802.11b/g/n Wireless LAN Controller
                vendor: Broadcom Corporation
                physical id: 0
                bus info: pci@0000:12:00.0
                logical name: eth1
                version: 01
                serial: 5c:ac:4c:6a:4c:52
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=wl0 driverversion=6.20.155.1 (r326264) ip=192.168.0.14 latency=0 multicast=yes wireless=IEEE 802.11abg
                resources: irq:17 memory:fbd00000-fbd03fff


2. *-network
                description: Ethernet interface
                product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:13:00.0
                logical name: eth0
                version: 02
                serial: f0:4d:a2:8f:91:99
                size: 10Mbit/s
                capacity: 100Mbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=N/A latency=0 link=no multicast=yes port=MII speed=10Mbit/s
                resources: irq:46 ioport:d000(size=256) memory:d0c10000-d0c10fff memory:d0c00000-d0c0ffff memory:fb300000-fb31ffff



ZEROF

  • Hero Member
  • *****
  • Posts: 1245
    • View Profile
    • Pen Tester
Reply #1 on: May 24, 2013, 12:08:10 PM
I don't have a lot of time but what you don't know or you don't see :

eth0 is for local internet network, that is not WiFi interface !!!

You are missing drivers for your Wifi card or adapter. I will check more soon, and give you more information, but you need to provide more information too.

Check this topic, and use pastebin to give all information :

http://forum.backbox.org/software-support/how-to-ask-for-wifi-adaptersdrivers-help-!-!-!/
« Last Edit: May 24, 2013, 12:16:07 PM by ZEROF »


Don't ask, read : http://wiki.backbox.org
or just run sudo rm -rf /*


weVeg

  • Hero Member
  • *****
  • Posts: 737
    • View Profile
Reply #2 on: May 24, 2013, 12:52:28 PM
Hi aronk!
As you can see your wireless card is labeled "eth1", check here [1] if your vendor is compatible with aircrack, or if your driver need to be patched. Isn't important if you use backtrack or kaly or bbox, all you need is aircrack!

[1] http://tinyurl.com/34c5m8

una voce libera è sempre liberatrice
under_r00t


aronk

  • Newbie
  • *
  • Posts: 5
    • View Profile
Reply #3 on: May 24, 2013, 01:12:29 PM



weVeg

  • Hero Member
  • *****
  • Posts: 737
    • View Profile
Reply #4 on: May 24, 2013, 01:23:21 PM
All you need is here:
driver=wl0 driverversion=6.20.155.1 (r326264)
product: BCM4313 802.11b/g/n Wireless LAN Controller
vendor: Broadcom Corporation
logical name: eth1

Read above and check your driver!

una voce libera è sempre liberatrice
under_r00t


ZEROF

  • Hero Member
  • *****
  • Posts: 1245
    • View Profile
    • Pen Tester
Reply #5 on: May 24, 2013, 02:43:25 PM
Try :

sudo modprobe brcmsmac


Don't ask, read : http://wiki.backbox.org
or just run sudo rm -rf /*


aronk

  • Newbie
  • *
  • Posts: 5
    • View Profile
Reply #6 on: May 24, 2013, 02:51:03 PM
All you need is here:
driver=wl0 driverversion=6.20.155.1 (r326264)
product: BCM4313 802.11b/g/n Wireless LAN Controller
vendor: Broadcom Corporation
logical name: eth1

Read above and check your driver!

Sorry, I didn't see your post when I forget to refresh the page ... I have read that theme and didn't understand a lot of it, I don't know what to do right know?



aronk

  • Newbie
  • *
  • Posts: 5
    • View Profile
Reply #7 on: May 24, 2013, 03:10:20 PM
Try :

sudo modprobe brcmsmac



I tried this, and after typed airmon-ng, the result is same:

Interface   Chipset      Driver

eth1      Unknown    wl - [phy0]


P.S. I follow these instructions: http://www.youtube.com/watch?v=qe1VuhGciSI and http://www.youtube.com/watch?v=7fI7qs9ZF40
is this good or I should try something else ?



weVeg

  • Hero Member
  • *****
  • Posts: 737
    • View Profile
Reply #8 on: May 24, 2013, 03:17:23 PM
check here [1] and [2] as reported you have to blacklist wl driver and install other ones, you have to learn how to do, we can't write all step for you.... Check aircrack wiki, all you need is there!
Try to follow the instruction and if you can't try to ask....
[1] http://www.aircrack-ng.org/doku.php?id=compatibility_drivers
[2] http://www.aircrack-ng.org/doku.php?id=b43&DokuWiki=734f25adbcaf72a28a7d97329a368209
« Last Edit: May 24, 2013, 03:20:03 PM by weVeg »

una voce libera è sempre liberatrice
under_r00t


aronk

  • Newbie
  • *
  • Posts: 5
    • View Profile
Reply #9 on: May 24, 2013, 07:05:28 PM
I typed: lspci -vnn | grep 14e4
from second link you gave me and the result is:


12:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)

ID is [14e4:4727] and it's not in the list below:

PCI ID    Driver   
14e4:4311    b43/wl   
14e4:4313   
14e4:4315   
14e4:4301    b43legacy   
14e4:4306   
14e4:4320   
14e4:4307     b43   
14e4:4312   
14e4:4318   
14e4:4319   
14e4:4320   
14e4:5354   

But it's last updated on 2010/12/01, maybe it's now available for [14e4:4727G], also I have 3.2.0-43-generic-pae kernel ...

Is there any other way to make all works succesful?





weVeg

  • Hero Member
  • *****
  • Posts: 737
    • View Profile
Reply #10 on: May 25, 2013, 12:11:09 AM
« Last Edit: May 28, 2013, 05:20:08 PM by ZEROF »

una voce libera è sempre liberatrice
under_r00t