Results 1 to 14 of 14

Thread: Kali and TL-WN722N nothing works :(

  1. #1
    Join Date
    2013-Nov
    Posts
    6

    Unhappy [Solved]Kali and TL-WN722N nothing works :(

    Hello,

    I've installed Kali on a VM on my mac but i cant make it work..

    This is my first time on Kali, Even on linux so its very hard to understand something ...



    Uploaded with ImageShack.us

    Tried lsusb, ifconfig wlan

    I dont really know what to do.. i looked after backtrack 5 but they were many troubles with that TP-LINK. I dont even did the update of kali

    So i have:

    Macbook pro 13" Mid-2012 Core i5 2,5GHz 16 GB Memory, 500 HDD, USB TP-LINK TL-WN722N

    Maverick 10.9
    Bootcamp Windows 7 Ultimate

    Running VM on Mac
    Last edited by martel_420; 2013-11-14 at 22:18.

  2. #2
    Join Date
    2013-Oct
    Posts
    56
    I have just bought this adapter and worked fine for me out of the box the first time but then I had a problem with it not being recognised so
    all I did was unplug it and and tried again and it worked no problem. You could also try putting it in another usb slot this has also worked for me.

    Have you disconnected it from the host in VMware - Menu-VM-Removable Devices - Atheros USB2.0 Wlan?

  3. #3
    Join Date
    2013-Nov
    Posts
    6
    Quote Originally Posted by flyinghaggis View Post
    I have just bought this adapter and worked fine for me out of the box the first time but then I had a problem with it not being recognised so
    all I did was unplug it and and tried again and it worked no problem. You could also try putting it in another usb slot this has also worked for me.

    Have you disconnected it from the host in VMware - Menu-VM-Removable Devices - Atheros USB2.0 Wlan?
    Hey Flying, thanks for the answear but i didnt worked for me.

    My adaptater is reconized with lsusb (atheros ...) but when i try iconfig wlanX up it say's "ERROR while getting interface flags: no such device"

    I tried unplug/plug again but still dont work, also tried by unpluging in the usb icone (the host) on virtual machine but still doesn't work

    I'm begginer i saw a tutorial on internet but it block at this part i can't install the usb wireless...

    When i put "airmon-ng" it show nothing (exept Interace/Chipset/drive) i dont know what/how to solved it
    Last edited by martel_420; 2013-11-07 at 09:11. Reason: spelling

  4. #4
    Join Date
    2013-Oct
    Posts
    56
    What are you actually typing - wlanx or the number associated with the wireless usb -i.e. wlan0 or wlan1?

    Try iwconfig that should tell you the number of the device - Wlan0,1 or 2
    When you have identified it type

    airmon-ng start Wlan0 or whatever number it has 0,1,2 at the end of the Wlan part.

  5. #5
    Join Date
    2013-Nov
    Posts
    6
    okay, so i did it but still nothing

    iwconfig -> no wireless extensions (ATHEROS clicked on the host icone/ tried unplug but no works)

    lsusb -> Device 005 Atheros okay..

    then i wrote airmon-ng start wlan5 ... and "error"..

  6. #6
    Join Date
    2013-Nov
    Posts
    6

  7. #7
    Join Date
    2013-Nov
    Posts
    1
    Hi there,
    i have the same problem - running Kali on a Raspberry Pi with the TP-Link TL-WN722N Adapter.

    When i do a "lsusb" it shows up as "Bus 001 Device 005: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n".
    But a "iwconfig" only tells me "wlan0 / lo / eth0 - no wireless extensions".
    I can do a "ifconfig wlan0 up" and it tells me "IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready" but afterwards wlan0 shows up when i do a "ifconfig".
    A "iwlist wlan0 scanning" tells me "wlan0 - Interface doesnt support scanning".
    Also a "airmon-ng start wlan0" only gives me the headers "Interface / Chipset / Driver" and nothing else.

    So somehow it is found but not usable.
    Any ideas?

    Any help is highly appreciated!

  8. #8
    Join Date
    2013-Nov
    Posts
    1
    Good day to everybody.
    Was anybody succesful in running wireless TP-Link TL-WN7222N (Atheros chipset) on Kali/Backtrack as VM? If yes, can you please help me out?
    Here is the output from console:

    root@kali:~# ifconfig
    eth0 Link encap:Ethernet HWaddr 08:00:27:7c:b6:32
    inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::a00:27ff:fe7c:b632/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:131 errors:0 dropped:0 overruns:0 frame:0
    TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:11534 (11.2 KiB) TX bytes:2400 (2.3 KiB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:12 errors:0 dropped:0 overruns:0 frame:0
    TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:720 (720.0 B) TX bytes:720 (720.0 B)


    root@kali:~# lsusb
    Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
    Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
    Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

    root@kali:~# iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.


    root@kali:~# cat /etc/network/interfaces
    # This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).

    # The loopback network interface
    auto lo
    iface lo inet loopback

    # The primary network interface
    allow-hotplug eth0
    iface eth0 inet dhcp

    auto wlan0
    iface wlan0 inet dhcp

    root@kali:~# service networking restart
    [....] Running /etc/init.d/networking restart is deprecated because it may not r[warnble some interfaces ... (warning).
    [....] Reconfiguring network interfaces...Internet Systems Consortium DHCP Client 4.2.2
    Copyright 2004-2011 Internet Systems Consortium.
    All rights reserved.
    For info, please visit https://www.isc.org/software/dhcp/

    Listening on LPF/eth0/08:00:27:7c:b6:32
    Sending on LPF/eth0/08:00:27:7c:b6:32
    Sending on Socket/fallback
    DHCPRELEASE on eth0 to 192.168.1.1 port 67
    Reloading /etc/samba/smb.conf: smbd only.
    Internet Systems Consortium DHCP Client 4.2.2
    Copyright 2004-2011 Internet Systems Consortium.
    All rights reserved.
    For info, please visit https://www.isc.org/software/dhcp/

    Cannot find device "wlan0"
    Bind socket to interface: No such device
    Failed to bring up wlan0.
    done.

    root@kali:~# dmesg
    ...
    [ 50.792109] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
    [ 339.404142] usb 1-2: new full-speed USB device number 3 using ohci_hcd
    [ 339.682791] usb 1-2: New USB device found, idVendor=0cf3, idProduct=9271
    [ 339.682791] usb 1-2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
    [ 339.682791] usb 1-2: Product: USB2.0 WLAN
    [ 339.682791] usb 1-2: Manufacturer: ATHEROS
    [ 339.682791] usb 1-2: SerialNumber: 12345
    [ 341.940154] cfg80211: Calling CRDA to update world regulatory domain
    [ 342.840153] cfg80211: World regulatory domain updated:
    [ 342.840153] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [ 342.840153] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 342.840153] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [ 342.840153] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [ 342.840153] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 342.840153] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [ 343.796020] usb 1-2: ath9k_htc: Firmware htc_9271.fw requested
    [ 343.796020] usbcore: registered new interface driver ath9k_htc
    [ 344.122870] usb 1-2: ath9k_htc: Firmware - htc_9271.fw download failed
    [ 344.122870] usb 1-2: ath9k_htc: USB layer deinitialized

    root@kali:~# modprobe -v ath9k_htc
    insmod /lib/modules/3.7-trunk-686-pae/kernel/net/rfkill/rfkill.ko
    insmod /lib/modules/3.7-trunk-686-pae/kernel/net/wireless/cfg80211.ko
    insmod /lib/modules/3.7-trunk-686-pae/kernel/net/mac80211/mac80211.ko
    insmod /lib/modules/3.7-trunk-686-pae/kernel/drivers/net/wireless/ath/ath.ko
    insmod /lib/modules/3.7-trunk-686-pae/kernel/drivers/net/wireless/ath/ath9k/ath9k_hw.ko
    insmod /lib/modules/3.7-trunk-686-pae/kernel/drivers/net/wireless/ath/ath9k/ath9k_common.ko
    insmod /lib/modules/3.7-trunk-686-pae/kernel/drivers/net/wireless/ath/ath9k/ath9k_htc.ko


    root@kali:~# ls -l /lib/firmware/ar*
    -rw-r--r-- 1 root root 70624 Jan 6 2013 /lib/firmware/ar7010_1_1.fw
    -rw-r--r-- 1 root root 70624 Jan 6 2013 /lib/firmware/ar7010.fw
    -rw-r--r-- 1 root root 15944 Jan 6 2013 /lib/firmware/ar9170.fw
    -rw-r--r-- 1 root root 51312 Jan 6 2013 /lib/firmware/ar9271.fw

    /lib/firmware/ar3k:
    total 220
    -rw-r--r-- 1 root root 55244 Jan 6 2013 AthrBT_0x01020001.dfu
    -rw-r--r-- 1 root root 40724 Jan 6 2013 AthrBT_0x01020200.dfu
    -rw-r--r-- 1 root root 19164 Jan 6 2013 AthrBT_0x01020201.dfu
    -rw-r--r-- 1 root root 36828 Jan 6 2013 AthrBT_0x11020000.dfu
    -rw-r--r-- 1 root root 40652 Jan 6 2013 AthrBT_0x31010000.dfu
    -rw-r--r-- 1 root root 1224 Jan 6 2013 ramps_0x01020001_26.dfu
    -rw-r--r-- 1 root root 1274 Jan 6 2013 ramps_0x01020200_26.dfu
    -rw-r--r-- 1 root root 1204 Jan 6 2013 ramps_0x01020200_40.dfu
    -rw-r--r-- 1 root root 264 Jan 6 2013 ramps_0x01020201_26.dfu
    -rw-r--r-- 1 root root 264 Jan 6 2013 ramps_0x01020201_40.dfu
    -rw-r--r-- 1 root root 1796 Jan 6 2013 ramps_0x11020000_40.dfu
    -rw-r--r-- 1 root root 1926 Jan 6 2013 ramps_0x31010000_40.dfu


    root@kali:~# lsmod | grep ath9k
    ath9k_htc 43135 0
    ath9k_common 12649 1 ath9k_htc
    ath9k_hw 313625 2 ath9k_common,ath9k_htc
    ath 17154 3 ath9k_common,ath9k_htc,ath9k_hw
    mac80211 287461 1 ath9k_htc
    cfg80211 123887 3 ath,mac80211,ath9k_htc
    usbcore 109555 4 ohci_hcd,ehci_hcd,usbhid,ath9k_htc


    Am i missing something simple? Will appreciate your help.
    Thanks
    --e

  9. #9
    Join Date
    2013-Nov
    Posts
    6
    i had a solution which i didnt tested yet: install the firwware ( firmware-realtek or firmware-ralink, i dont remeber ) from non free issues.

    http://docs.kali.org/troubleshooting...-driver-issues

    Then check dmesg on boot

    i'll check that soon, if someone can check it and post a solution it would be fine, thx

  10. #10
    TP-W8200ND neither... i tested on Backtrack 5 R3 and kali and doesnt work...

  11. #11
    Join Date
    2013-Nov
    Posts
    6
    Looks like i have the solution Works for me ^^

    i did on the terminal:

    "dmesg"

    then it showed me

    http://img834.imageshack.us/img834/888/88uk.jpg

    At this time i did any manipulation

    Then i tried to install the "htc_9271.fw" with this link:

    http://wireless.kernel.org/download/htc_fw/1.3/
    (you have to choose your link "htc_9271" or the firmware of your use wireless then download it.

    In terminal, wrote "gksu nautilus", which gives you full folder access. I paste the htc_9271.fw file on the /library/firmware (i dont know why but i had already the file on the firmware folder :/ maybe due to "dmseg" ??)


    Close all, write airmon-ng -> Normally, it will show you the atheros on the chipstet/drivers/etc...

    Enjoy
    Last edited by martel_420; 2013-11-15 at 00:30.

  12. #12
    Join Date
    2013-Dec
    Posts
    2
    Quote Originally Posted by martel_420 View Post
    Looks like i have the solution Works for me ^^

    i did on the terminal:

    "dmesg"

    then it showed me

    http://img834.imageshack.us/img834/888/88uk.jpg

    At this time i did any manipulation

    Then i tried to install the "htc_9271.fw" with this link:

    http://wireless.kernel.org/download/htc_fw/1.3/
    (you have to choose your link "htc_9271" or the firmware of your use wireless then download it.

    In terminal, wrote "gksu nautilus", which gives you full folder access. I paste the htc_9271.fw file on the /library/firmware (i dont know why but i had already the file on the firmware folder :/ maybe due to "dmseg" ??)


    Close all, write airmon-ng -> Normally, it will show you the atheros on the chipstet/drivers/etc...

    Enjoy
    Hmm...I am having the EXACT same problems as you were, but using that downloaded .fw file did not help me...

  13. #13
    Join Date
    2014-Mar
    Location
    new delhi
    Posts
    7
    Quote Originally Posted by flyinghaggis View Post
    You could also try putting it in another usb slot this has also worked for me.
    pheeww man!! after 3 hours of googling and numerous videos, i found your comment.thnxxx worked

  14. #14
    Join Date
    2015-Oct
    Posts
    1
    It worked for me too
    Maybe is the action of unplug & plug... THANK YOU (MBP Late 2011 El Capitan as Host, and KALI as Guest of course)

Similar Threads

  1. TP-LINK TL-WN722N and OnePlus One sometimes works, often doesn't. At wits end!
    By nethunterissues in forum NetHunter General Questions
    Replies: 3
    Last Post: 2016-09-19, 15:13
  2. TP-LINK WN722N works great, TP-LINK WN822N does not.
    By Diluted in forum NetHunter General Questions
    Replies: 1
    Last Post: 2016-01-29, 23:55
  3. Replies: 1
    Last Post: 2015-05-08, 02:13
  4. DNS problem: ping works, nslookup works, wget and browser do not.
    By thinker in forum TroubleShooting Archive
    Replies: 8
    Last Post: 2013-06-30, 06:01

Posting Permissions

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