Results 1 to 8 of 8

Thread: "airmon-ng" Does not give an interface

  1. #1
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    4

    Default "airmon-ng" Does not give an interface

    So I downloaded Backtrack 4 and am stuck once again. Here are my laptops specs.

    Model Name: MacBook Pro
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.8 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 6 MB
    Memory: 4 GB

    First I tried kisMAC which led me to a wall when it came to injecting packets. I was able to make it monitor after some tweaking but airport extreme cards will not inject packets and no one has written a driver to make it happen. I did read somewhere that backtrack had the capability of making it happen so I went ahead and downloaded backtrack 4 and gave it a whirl.

    When I enter airmon-ng I am given three columns with no information (Interface, Chipset, Driver). Looking around has had me try a great deal of things. So I apologize if I leave something out.

    I have..

    Tried using the Wireless LAN Manager.
    That was the first program to pick up any interface at all. "eth0"

    ifconfig X up
    x being wifi0, ath0, eth0, and lo. lo was the only one that did something different. Different meaning it did nothing at all rather than returning the "no such device" error. Putting it down does nothing either.

    iwconfig
    That brought back "no wireless extensions" for lo and eth0.



    Thought maybe it was the connection to vmware..
    That search brought about the command "lspci". That returned a very long response.. That led to no results in google.

    bt ~ # lspci
    00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (
    rev 01)
    00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (re
    v 01)
    00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)
    00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
    00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
    00:07.7 System peripheral: VMware Inc Virtual Machine Communication Interface (r
    ev 10)
    00:0f.0 VGA compatible controller: VMware Inc Abstract SVGA II Adapter
    00:10.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-
    MPT Dual Ultra320 SCSI (rev 01)
    00:11.0 PCI bridge: VMware Inc Unknown device 0790 (rev 02)
    00:15.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:15.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:16.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:17.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.0 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.1 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.2 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.3 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.4 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.5 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.6 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    00:18.7 PCI bridge: VMware Inc Unknown device 07a0 (rev 01)
    02:00.0 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB
    02:01.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)
    02:02.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 02)
    02:03.0 USB Controller: VMware Inc Abstract USB2 EHCI Controller



    Then I thought it might be the iso. So I went ahead and downloaded BT3 thinking it may be more stable. That yielded the same results.

    I would just like to have the answer to what seems like a very simple task. Or at least a nice push in the right direction to continue trying new things.

    If you need more information or for me to test something just let me know.

    Thanks in advance.

  2. #2
    Very good friend of the forum Gitsnik's Avatar
    Join Date
    Jan 2010
    Location
    The Crystal Wind
    Posts
    851

    Default

    As you want a very simple answer I am going to give you two very simple options:

    1. Buy a compatible USB wireless card, read the manuals, read some threads around here about VMWare, and post back with your results. I know this method works.

    2. Get a different laptop that is not a Mac, and has all the correct wifi hardware in it. I know this method works as well.
    Still not underestimating the power...

    There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

  3. #3
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    4

    Default

    So those are my only two options? Nothing I can do without purchasing more?

  4. #4
    Very good friend of the forum Gitsnik's Avatar
    Join Date
    Jan 2010
    Location
    The Crystal Wind
    Posts
    851

    Default

    Quote Originally Posted by Fury M View Post
    So those are my only two options? Nothing I can do without purchasing more?
    Pretty much. If you get lucky sometimes the interface will permit injection if the about-this-mac info shows the right kit, but even then KisMAC and the other programs are a PiTA to work with when it comes to injection.

    Do yourself a favour and get another device, I use an EeePC when doing wifi audits and my macbook for the rest of the time, but a USB stick and VMWare is usually good. Barry has experience with this as well, but generally the Mac's are just a PITA to work with for anything other than OS X.

    Which, incidentally, is why I yell at my education clients when they try to dual boot the things.

    The other option is to not bother trying to crack wifi. We know it's vulnerable and there are a hundred video's out there to prove it. If you want to know if your WPA is vulnerable, download some WPA-wordlists and type:
    Code:
    grep "mypasswordbetweenthequotes" wordlist.lst
    to see if it would be cracked.
    Still not underestimating the power...

    There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

  5. #5
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    4

    Default

    Alright. Thanks a lot for pointing me in the right direction.

  6. #6
    Member imported_vvpalin's Avatar
    Join Date
    Apr 2009
    Posts
    442

    Default

    Sorry but i just noticed this ... are you using vmware and trying to get your INTERNAL wifi setup ???

    Because ... well, im gonna let someone else give you the talking to but short and sweet ... that shit aint gonna work sorry.
    Using backtrack for the first time is like being 10 years old again with the keys to a Ferrari.

  7. #7
    Senior Member
    Join Date
    Aug 2007
    Posts
    916

    Default

    I did not want to make a comment on this thread initially but even if you tried dualbooting with linux, chances are the wireless chipset on your macbook is broadcom.. and if its broadcom 802.11n capable chipset (in which chance I'm willing to bet with my 0.02 cents) it won't work with linux at all.

    So vmware: definitely no
    dualboot: if its not detected initially by b43 (i.e. no wlan0 interface) and its not a 14e4:4315 (bcm4315 lp-phy, often confused as bcm4312) then it won't work with linux natively.

  8. #8
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    4

    Default

    Yeah I went ahead and looked it up to confirm. Just in case someone else pulls this up one day and wanted to know if you were right.

    Interfaces:
    en1:
    Card Type: AirPort Extreme (0x14E4, 0x8D)
    Firmware Version: Broadcom BCM43xx 1.0 (5.10.91.26)

    I decided to do what Gitsnik said and just get a new machine. They are fairly inexpensive from what I have looked up on them.

Posting Permissions

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