unclespam
2018-11-18, 00:34
3219
Hello,
According to a few different sites the USB-AC56 should be able do go into monitor mode.
this site explicitly says so https://www.asus.com/us/Networking/USBAC56/
this guys reported success with the same card https://forums.kali.org/showthread.php?22578-Going-to-buy-a-802-11ac-wireless-adaptor
this site also explicitly says so https://www.acrylicwifi.com/en/support-webinars-wifi-wireless-network-software-tools/compatible-hardware/
I have Kali installed directly on this laptop (just to make it as easy as possible. I'm just learning).
I buy the card. First I try the drivers from Asus' site https://www.asus.com/us/Networking/USBAC56/HelpDesk_Download/. ./install.sh fails:
: error: ?_timer {aka struct timer_list}? has no member named ?data? ptimer->data = (unsigned long)cntx;
Which led me to an askubuntu (https://askubuntu.com/questions/1042399/make-modules-error-2) about a similar error. From the errors in the console I was able to determine that I needed drivers for the rtl8812AU chipset and that, finally, led me to a working driver (https://github.com/diederikdehaas/rtl8812AU/)
Now I can see and use the USB-AC56! But it won't get into monitor mode :mad:. I figure out which one it is by running
iwconfig, unplugging it, and running
iwconfig again. First I run
iw list to see if monitor mode is supported and if I am reading this right, yes it is supported:
Supported interface modes: * IBSS
* managed
* AP
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Then I do:
ifconfig wlan1 down
iwconfig wlan1 mode monitor
fconfig wlan1 up
iw list
and that gives:
wlan1 unassociated Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
so it's not in monitor mode. Similiarly, if I select that NIC in Wireshark, then Stop, then Capture Options, then click the monitor mode checkbox it immediately unchecks itself. Can you help a brotha-er out?
Hello,
According to a few different sites the USB-AC56 should be able do go into monitor mode.
this site explicitly says so https://www.asus.com/us/Networking/USBAC56/
this guys reported success with the same card https://forums.kali.org/showthread.php?22578-Going-to-buy-a-802-11ac-wireless-adaptor
this site also explicitly says so https://www.acrylicwifi.com/en/support-webinars-wifi-wireless-network-software-tools/compatible-hardware/
I have Kali installed directly on this laptop (just to make it as easy as possible. I'm just learning).
I buy the card. First I try the drivers from Asus' site https://www.asus.com/us/Networking/USBAC56/HelpDesk_Download/. ./install.sh fails:
: error: ?_timer {aka struct timer_list}? has no member named ?data? ptimer->data = (unsigned long)cntx;
Which led me to an askubuntu (https://askubuntu.com/questions/1042399/make-modules-error-2) about a similar error. From the errors in the console I was able to determine that I needed drivers for the rtl8812AU chipset and that, finally, led me to a working driver (https://github.com/diederikdehaas/rtl8812AU/)
Now I can see and use the USB-AC56! But it won't get into monitor mode :mad:. I figure out which one it is by running
iwconfig, unplugging it, and running
iwconfig again. First I run
iw list to see if monitor mode is supported and if I am reading this right, yes it is supported:
Supported interface modes: * IBSS
* managed
* AP
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Then I do:
ifconfig wlan1 down
iwconfig wlan1 mode monitor
fconfig wlan1 up
iw list
and that gives:
wlan1 unassociated Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
so it's not in monitor mode. Similiarly, if I select that NIC in Wireshark, then Stop, then Capture Options, then click the monitor mode checkbox it immediately unchecks itself. Can you help a brotha-er out?