Kali Linux/USB Wireless Adapter/No APs detected

Discussions related to using VirtualBox on Windows hosts.
Post Reply
TECH_N9NE
Posts: 2
Joined: 23. Nov 2021, 23:00

Kali Linux/USB Wireless Adapter/No APs detected

Post by TECH_N9NE »

I'm running VirtualBox 6.1.28 with Kali Rolling (2020.4) x64 and attempting to utilize the UBS wireless adapter from host OS.

I can see the the guest OS recognizes and captures the USB device:

$ lsusb
Bus 001 Device 002: ID 0bda:818b Realtek Semiconductor Corp. RTL8192EU 802.11b/g/n WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

And device appears to be UP:

$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 08:00:27:ab:08:1c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 8 bytes 400 (400.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 400 (400.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 9a:67:c9:d1:22:02 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off

However, under the Network Manager UI there are no Access Points listed under WiFi.

I ran a few more commands but I'm not sure how to interpret outputs as I'm not familiar with airmon-ng tool:

$ sudo airmon-ng check kill
[sudo] password for kali:

Killing these processes:

PID Name
629 wpa_supplicant


$ sudo airmon-ng start wlan0


PHY Interface Driver Chipset

phy1 wlan0 rtl8xxxu Realtek Semiconductor Corp. RTL8192EU 802.11b/g/n WLAN Adapter
(monitor mode enabled)


$ sudo airmon-ng start wlan0


PHY Interface Driver Chipset

phy1 wlan0 rtl8xxxu Realtek Semiconductor Corp. RTL8192EU 802.11b/g/n WLAN Adapter
(mac80211 monitor mode already enabled for [phy1]wlan0 on [phy1]wlan0)



$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 08:00:27:ab:08:1c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 8 bytes 400 (400.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 400 (400.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
unspec 00-13-EF-50-44-13-00-7E-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0



I noticed that after the airmon-ng commands my Network Manager is no longer running :-/

I have read through the UBS filtering + tips and tricks as outlined in the following thread: [removed - new user rule "You must be a member for 1 days and have 1 posts before you can post urls"] *eye_roll*

Attaching VBox.log and outputs from Windows commands:

C:\Program Files\Oracle\VirtualBox>VBoxManage -version
6.1.28r147628

C:\Program Files\Oracle\VirtualBox>VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 6.1.28
Revision: 147628
Edition:
Description: Oracle Cloud Infrastructure integration, USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module: VBoxVRDP
Usable: true
Why unusable:

C:\Program Files\Oracle\VirtualBox>VBoxManage list usbhost
Host USB Devices:

UUID: dc186985-88cf-411e-a06c-281bce1935ca
VendorId: 0x1130 (1130)
ProductId: 0x1620 (1620)
Revision: 1.135 (01135)
Port: 6
USB version/speed: 1/Full
Manufacturer: Tenx Technology, Inc.
Product: USB AUDIO
Address: {36fc9e60-c465-11cf-8056-444553540000}\0014
Current State: Busy

UUID: 540eb8e5-7cde-4ce7-8cbf-0b4dd03e6d9e
VendorId: 0x0bda (0BDA)
ProductId: 0x818b (818B)
Revision: 2.0 (0200)
Port: 1
USB version/speed: 2/High
Manufacturer: Realtek
Product: 802.11n NIC
SerialNumber: 00e04c000001
Address: {4d36e972-e325-11ce-bfc1-08002be10318}\0002
Current State: Busy

UUID: 5a844fed-4966-402c-970d-455f1743b79d
VendorId: 0x04d9 (04D9)
ProductId: 0x1603 (1603)
Revision: 3.16 (0316)
Port: 2
USB version/speed: 1/Low
Manufacturer:
Product: USB Keyboard
Address: {36fc9e60-c465-11cf-8056-444553540000}\0017
Current State: Busy

UUID: 945807f5-5870-433b-9a68-c47d7beba6f2
VendorId: 0x045e (045E)
ProductId: 0x0040 (0040)
Revision: 3.0 (0300)
Port: 5
USB version/speed: 1/Low
Manufacturer: Microsoft
Product: Microsoft 3-Button Mouse with IntelliEye(TM)
Address: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0007
Current State: Busy


C:\Program Files\Oracle\VirtualBox>VBoxManage list usbfilters
Global USB Device Filters:

<none>


C:\Program Files\Oracle\VirtualBox>VBoxManage showvminfo "Kali-Linux-2020.4-vbox-amd64"
Name: Kali-Linux-2020.4-vbox-amd64
Groups: /
Guest OS: Windows 7 (64-bit)
UUID: 82a0e95e-f0dd-43a3-91a6-f5decb0d52ef
Config file: C:\Users\Ian\VirtualBox VMs\Kali-Linux-2020.4-vbox-amd64\Kali-Linux-2020.4-vbox-amd64.vbox
Snapshot folder: C:\Users\Ian\VirtualBox VMs\Kali-Linux-2020.4-vbox-amd64\Snapshots
Log folder: C:\Users\Ian\VirtualBox VMs\Kali-Linux-2020.4-vbox-amd64\Logs
Hardware UUID: 82a0e95e-f0dd-43a3-91a6-f5decb0d52ef
Memory size: 2048MB
Page Fusion: disabled
VRAM size: 128MB
CPU exec cap: 100%
HPET: disabled
CPUProfile: host
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
PAE: enabled
Long Mode: enabled
Triple Fault Reset: disabled
APIC: enabled
X2APIC: enabled
Nested VT-x/AMD-V: disabled
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode: message and menu
Boot Device 1: Floppy
Boot Device 2: DVD
Boot Device 3: HardDisk
Boot Device 4: Not Assigned
ACPI: enabled
IOAPIC: enabled
BIOS APIC mode: APIC
Time offset: 0ms
RTC: UTC
Hardware Virtualization: enabled
Nested Paging: enabled
Large Pages: enabled
VT-x VPID: enabled
VT-x Unrestricted Exec.: enabled
Paravirt. Provider: Default
Effective Paravirt. Prov.: HyperV
State: powered off (since 2021-11-23T21:43:09.737000000)
Graphics Controller: VBoxSVGA
Monitor count: 1
3D Acceleration: disabled
2D Video Acceleration: disabled
Teleporter Enabled: disabled
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: disabled
Allow Tracing to Access VM: disabled
Tracing Configuration:
Autostart Enabled: disabled
Autostart Delay: 0
Default Frontend:
VM process priority: default
Storage Controller Name (0): SATA
Storage Controller Type (0): IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 30
Storage Controller Port Count (0): 1
Storage Controller Bootable (0): on
SATA (0, 0): C:\Users\Ian\VirtualBox VMs\Kali-Linux-2020.4-vbox-amd64\Kali-Linux-2020.4-vbox-amd64-disk001.vdi (UUID: 2ae5dfc7-e036-4984-9344-88db8b423afd)
NIC 1: MAC: 080027AB081C, Attachment: NAT, Cable connected: off, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: allow-vms, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
UART 3: disabled
UART 4: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: DSOUND, Controller: AC97, Codec: AD1980)
Audio playback: enabled
Audio capture: disabled
Clipboard Mode: Bidirectional
Drag and drop Mode: Bidirectional
VRDE: disabled
OHCI USB: enabled
EHCI USB: enabled
xHCI USB: disabled

USB Device Filters:

Index: 0
Active: yes
Name: Realtek Semiconductor Corp. ACT-WNP-UA-005 802.11b/g/n WLAN Adapter [0200]
VendorId: 0bda
ProductId: 818b
Revision:
Manufacturer:
Product:
Remote:
Serial Number:

Bandwidth groups: <none>

Shared folders:<none>

Capturing: active
Capture audio: not active
Capture screens: 0
Capture file: C:\Users\Ian\VirtualBox VMs\Kali-Linux-2020.4-vbox-amd64\Kali-Linux-2020.4-vbox-amd64.webm
Capture dimensions: 1024x768
Capture rate: 512kbps
Capture FPS: 25kbps
Capture options: vc_enabled=true,ac_enabled=false,ac_profile=med

Description:
Kali Rolling (2020.4) x64
2020-11-17

- - - - - - - - - - - - - - - - - -

Username: kali
Password: kali
(US keyboard layout)
Attachments
VBox.zip
(29.67 KiB) Downloaded 4 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Kali Linux/USB Wireless Adapter/No APs detected

Post by scottgus1 »

Thanks for sending the "USB Basics" info, all the USB configuration looks good!

The adapter is getting into the VM:
VendorId: 0x0bda (0BDA)
ProductId: 0x818b (818B)
Revision: 2.0 (0200)
Port: 1
USB version/speed: 2/High
Manufacturer: Realtek
...
00:00:07.010663 VUSB: Attached '00000000067be210[proxy 0bda:818b]' to port 1 on RootHub#0 (HighSpeed)
00:17:34.995923 VUSB: Detached '00000000067be210[proxy 0bda:818b]' from port 1 on RootHub#0
...
$ lsusb
Bus 001 Device 002: ID 0bda:818b Realtek Semiconductor Corp. RTL8192EU 802.11b/g/n WLAN Adapter
One glitch in the VM configuration, though I doubt it causes this problem:
00:00:03.766572 Guest OS type: 'Windows7_64'
00:00:21.001398 VMMDev: Guest Log: 21:10:21:10:34.095619 main OS Product: Linux
00:00:21.001924 VMMDev: Guest Log: 21:10:34.096052 main OS Release: 5.9.0-kali1-amd64
Paravirtualization:
00:00:03.825699 GIM: Using provider 'HyperV' (Implementation version: 0)
The name "Kali" does not recognize in the New VM wizard, and your VM's template remained on Windows 7, with Windows-based paravirtualization. Kali is a Debian-based Linux, and should be using KVM paravirtualization. You could try fixing this in the VM's General settings, Basic tab, and System settings, Acceleration tab.

However, I don't think the template would cause this problem.

This appears to be only configuration issues inside Kali, and you'll probably have to web-search Kali forums and help materials to get the adapter running.
TECH_N9NE wrote:I have read through the UBS filtering + tips and tricks as outlined in the following thread: [removed - new user rule "You must be a member for 1 days and have 1 posts before you can post urls"] *eye_roll*
As a new forum user, it's better to ask why things are done a certain way before expressing opinion about it. Actually it's better as a new person in any situation to see why things are done a certain way before complaining.

The first-day-first-post rule stops a whole trainload of spam. All possible things that need be posted on the first day first post can be posted (many times when zipped) through the forum's Upload Attachment tab.
TECH_N9NE
Posts: 2
Joined: 23. Nov 2021, 23:00

Re: Kali Linux/USB Wireless Adapter/No APs detected

Post by TECH_N9NE »

Thanks for reply scottgus1.

I switched to KVM paravirtualization and tried network connection again but same results.

Since this appears to be a Kali problem and not a VirtualBox problem, I'll seek further assistance in Kali Linux forums. Cheers.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Kali Linux/USB Wireless Adapter/No APs detected

Post by scottgus1 »

Sounds good! Hope you get the stick working!
Post Reply