Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Discussions related to using VirtualBox on Windows hosts.

Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 14. Jun 2021, 13:41

I'm having trouble making bridged networking work with a USB wifi adapter.

My system/setup:
Windows 10 laptop(On board network cards: Inter(R) Wi-Fi 6 AX200 160MHz, Realtek PCI Ethernet)

Virtualbox(6.1.22 r144080 with same version Extension Pack)with:
-Kali Linux vm
-Metasploitable 2 vm

-TP-Link Wireless USB adapter(Realtek 802.11ac NIC [0210])
-Realtek 802.11ac WLAN Adapter [0200](RTL8811AU)

First i tried the bridged network setting with my on-board wifi card but that didn't work.

So i borrowed two USB wifi adapters and tried bridged networking with those

I tried selecting them under Devices>USB:

But that didn't work. So i tried adding a new filter under Settings>USB

But after i created the filter i can't select it as an adapter in Settings>Network

The USB adapters are recognized by Kali:

root@kali:~# lsusb
Bus 001 Device 002: ID 0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac 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

root@kali:~# lsusb
Bus 001 Device 002: ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
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

But i don't get a connection. The network manager in Kali says disconnected and doesn't show an option for a wifi(only Wired connection1)connection

I'm fairly new to this, but i've been at this for days. So any help would be much appreciated.

ps. The only way i've been able to make bridged networking work is by selecting my Ethernet adapter and connecting with a Ethernet cable. But i need to use wifi with my Kali vm in the future.
ps2. I can't use NAT because i need to be able to recieve incoming connections to my Kali machine.
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby scottgus1 » 14. Jun 2021, 13:55

Bridged does not always work with host-operated Wi-Fi, see Virtualbox Networks: In Pictures: Bridged Adapter.

Even when Bridged does work with the host's Wi-Fi, the VM will only see a wired Ethernet adapter, because Virtualbox only simulated wired adapters for the VM. There is no correlation between host and VM hardware, except for the CPU.

The only way to get Wi-Fi into a VM is through a USB adapter and proper Virtualbox USB filter. The VM OS also needs drivers and proper OS-specific configuration for the device. Virtualbox cannot Bridge to any network device passed via USB into the VM, since the VM now has direct control of the device. Carefully go through USB basics and troubleshooting. If you finish all the steps 1-7 and cannot get your USB device into the guest OS, carefully post the outputs of the commands in step 8 as text in [code] tags, not screenshots. Zip and post the logs step 8 call for, using the forum's Upload Attachment tab.
scottgus1
Site Moderator
 
Posts: 12471
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 17. Jun 2021, 14:36

Thnx for your reaction! I'm on vacation right now but when i get back i will try the 7/8 steps.

I've tried this:
https://null-byte.wonderhowto.com/forum ... x-0324433/
https://www.youtube.com/watch?v=6KqR5gxAm8s

But if i read the following correctly:

Virtualbox Networking in Pictures wrote:The physical host network adapter that Bridged is using must be "up", that is, connected to something, so that the lights are flashing, even if it is another device that is not set up correctly for the host network. If the physical adapter is "down", Bridged will not start


What does 'up' mean in this description? I have an onboard wifi which is up/connected and when i connect one of the usb adapters Windows sees them in Network status>adapteroptions but it is not connected to a wifi. Should i connect the usb wifi adapter to my wifi network first before trying bridged networking?
Last edited by scottgus1 on 18. Jun 2021, 17:18, edited 3 times in total.
Reason: added quote tags
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby scottgus1 » 18. Jun 2021, 17:17

"Up" means an active network connection (usually shown by the little lights at the ethernet jack on the back of the computer blinking normally). Linux often denotes an active network connection in Terminal commands 'ifconfig' or 'ip address' as "up". It refers to a wired Ethernet connection.

scottgus1 wrote:Virtualbox cannot Bridge to any network device passed via USB into the VM, since the VM now has direct control of the device.

The USB Wi-Fi adapter should be passed into the VM OS though a Virtualbox USB filter. Then the VM OS will see it and run it directly in the VM OS. The USB Filter will let the VM see Wi-Fi. The host will not see the USB Wi-Fi adapter when the Virtualbox USB Filter is configured and working correctly, so you will not Bridge to the USB Wi-Fi adapter on the host.
scottgus1
Site Moderator
 
Posts: 12471
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 30. Jun 2021, 13:16

I'm back from vacation and carefully reading USB basics and Troubleshooting but i'm having trouble creating and using a proper filter;

I've created a filter with only VendorID and productID as described but the last steps i can't get working.

4.Unplug the device.
After that under Network > Bridged adapter I select the USB wifi adapter:

Realtek RTL8811AU Wireless LAN 802.11ac USB 2.0 Network adapter, but i don't see the filter i created in the list of adapters. Shouldn't it show up there? Others in the list are:

- Intel(R) Wi-Fi 6 AX200 160MHz
- Realtek PCI Ethernet


5.Start your guest (the one that you applied the filter to). Let it start completely. Log in if you have to, reach the desktop, and wait until any disk activity has stopped.
When i start my guest VM with my USB wifi adapter unplugged it says it can't start up the VM because the Realtek networkinterface cannot be found. Should i select one of the other adapters to startup and then plug the USB wifi adapter? That didn't work either..

6. Plug your device. The filter should capture it and pass control to your guest.

I'm confused on what to do next. If needed i can post logs and output of the commands of steps 7 and 8 of the USB basics and troubleshooting guide..but then i need to make the filter to work first i guess?
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby scottgus1 » 30. Jun 2021, 16:59

Sceolan wrote:4.Unplug the device.
After that under Network > Bridged adapter I select the USB wifi adapter:

Realtek RTL8811AU Wireless LAN 802.11ac USB 2.0 Network adapter, but i don't see the filter i created in the list of adapters. Shouldn't it show up there?

You will not see the Virtualbox USB filter under the Bridged adapters to use. The USB filters only show in the USB tab, not the network tab.

After the device is unplugged you will not see it under the Bridged adapters to use. It is unplugged, the host no longer is running it so Virtualbox cannot Bridge to it.

Sceolan wrote:When i start my guest VM with my USB wifi adapter unplugged it says it can't start up the VM because the Realtek networkinterface cannot be found.

A VM will not start if it is set to Bridge to an adapter that is not present. You unplugged it in step 4, so the device cannot be Bridged to at startup of the VM.

You are confusing two different ideas: Bridging to a host network adapter, and passing a USB adapter into the VM.
scottgus1 wrote:The host will not see the USB Wi-Fi adapter when the Virtualbox USB Filter is configured and working correctly, so you will not Bridge to the USB Wi-Fi adapter on the host.

If you continue to desire to use the USB filter to get Wi-Fi in the VM, you will not bridge to the USB Wi-FI device. it is either one or the other, not both.

Don't Bridge to the USB Wi-Fi adapter.

Get the USB filter set up, follow the steps in the tutorial. Don't use Bridged in the VM's network adapters. Once the USB filter is working the VM OS will directly control the Wi-Fi device.
scottgus1
Site Moderator
 
Posts: 12471
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 3. Jul 2021, 16:30

Thnx again for your reply. I understand now the filter shouldn't show up under network adapters but i'm having trouble following the rest of your technical explanation.

You are saying don't use bridged networking, but i think i have no other choice. I'm trying to use Metasploit from within my Kali vm and run exploits on the intentionally vurnerable Metasploitable 2 machine. Several exploits i run try to open up a shell with a connection back to the Kali linux vm. That's why i said NAT or Host-only doesn't work. As also shown here in table 6.1:

https://www.virtualbox.org/manual/ch06. ... rkingmodes

After that i read this:

viewtopic.php?f=6&t=98133 1. For full on-the-LAN access, use wired Ethernet, or get a USB wi-fi adapter for the guest to use. So that's why i tried

And as i said earlier i was only able to make bridged networking work with a physical ethernet cable but i bougth this laptop to be able to sit in a library and other locations and use their wifi

"If you continue to desire to use the USB filter to get Wi-Fi in the VM, you will not bridge to the USB Wi-FI device. it is either one or the other, not both."

I understand it's one ore both but I continue to want to try to use the USB filter but what network adapter setting should i select then? I've tried them all. And one should be selected rigth?

The USB wifi adapter gets captured by the guest when i start the Kali vm with for instance NAT but then i can't reach a shell connection back to the Kali vm..

Sorry if this is a noob question, but i'm still confused. After this i will go through the whole tutorial in USB and Troubleshooting..
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby scottgus1 » 3. Jul 2021, 20:06

Sceolan wrote:Sorry if this is a noob question, but i'm still confused.

Don't worry, it's an interesting challenge getting this going.

OK, so I'm gathering that you want to hack the Metasploitable VM from the Kali VM, and you want to do it over Wi-Fi.

Bridged will not make the adapter inside the VM look like a Wi-Fi adapter, even if you were able to Bridge to the host Wi-Fi or a USB Wi-Fi adapter attached to the host OS. All Virtualbox-provided virtual adapters inside the VMs through Bridged, NAT, or any other Virtualbox network type will always look like wired Ethernet. The only way to see a Wi-Fi adapter inside the VM is with a USB filter and a USB Wi-Fi device.
Sceolan wrote:I continue to want to try to use the USB filter but what network adapter setting should i select then?

You wouldn't use any Virtualbox-provided network adapter in the VM if you use a USB filter to pass the USB Wi-Fi device into the VM. You can turn all the Virtualbox network adapters off.

To hack Metasploitable from Kali and have both VMs see a Wi-Fi adapter, you need two USB Wi-Fi adapters, one to go through a USB filter into the Kali, and one through a different USB filter to go into the Metasploitable. To make this easiest, buy a different company's Wi-Fi adapter, so you don't have two identical USB devices to try to filter differently.

If you don't want to get another USB Wi-Fi adapter, try booting your host from Kali and run Metasploitable as a VM inside Kali, with the USB filter passing the USB Wi-Fi adapter to Metasploitable, and Kali using the host Wi-Fi.
scottgus1
Site Moderator
 
Posts: 12471
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 4. Jul 2021, 14:33

Thnx again! It's getting clearer now. I've tried to launch the Linux VM with all the Virtualbox network adapters off. The USB filter captures the USB wifi adapter and the VM starts up but i can't get a connection.

So i went through the tutorial USB basics and troubleshooting. Before that i've tried to install drivers for my wifi adapter within Kali with:

wget https://http.kali.org/kali/pool/contrib ... i2_all.deb https://http.kali.org/kali/pool/contrib ... i1_all.deb
sudo apt update
sudo apt install ./realtek-rtl88xxau-dkms_5.6.4.2~git20210327.c0ce817-0kali2_all.deb ./realtek-rtl8814au-dkms_5.8.5.1~git20210331.bdf80b5-0kali1_all.deb

root@kali:~# lsusb
Bus 001 Device 002: ID 0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac WLAN Adapter

root@kali:~# dkms status
realtek-rtl8814au, 5.8.5.1~git20210331.bdf80b5: added
realtek-rtl88xxau, 5.6.4.2~git20210327.c0ce817: added
virtualbox-guest, 6.1.22: added

After that i followed the steps in section 8 of USB basics and Troubleshooting:
The zips of the log files are added as well. I hope someone can help find out what's going wrong

Output commands:
C:\Program Files\Oracle\VirtualBox>VBoxManage -version
6.1.22r144080

C:\Program Files\Oracle\VirtualBox>VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 6.1.22
Revision: 144080
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:

Host USB Devices:

UUID: 703232c9-bba5-45a3-9ceb-3c7a8a9357b5
VendorId: 0x8087 (8087)
ProductId: 0x0029 (0029)
Revision: 0.1 (0001)
Port: 3
USB version/speed: 2/Full
Manufacturer: Intel Corp.
Address: {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}\0000
Current State: Busy

UUID: 5002c205-3889-4729-9cab-0080d9c5baba
VendorId: 0x0bda (0BDA)
ProductId: 0xa811 (A811)
Revision: 2.0 (0200)
Port: 2
USB version/speed: 2/High
Manufacturer: Realtek
Product: 802.11ac WLAN Adapter
SerialNumber: 00e04c000001
Address: {4d36e972-e325-11ce-bfc1-08002be10318}\0020
Current State: Busy

UUID: 44005534-1a4d-4e84-a854-e790949ee414
VendorId: 0x0bda (0BDA)
ProductId: 0xa811 (A811)
Revision: 2.0 (0200)
Port: 2
USB version/speed: 2/High
Manufacturer: Realtek Semiconductor Corp.
Address: {4d36e972-e325-11ce-bfc1-08002be10318}\0020
Current State: Captured

UUID: 135aa4c0-b183-4312-9ec1-1fe96461cfe1
VendorId: 0x04f2 (04F2)
ProductId: 0xb6c2 (B6C2)
Revision: 39.20 (3920)
Port: 3
USB version/speed: 2/High
Manufacturer: Chicony Electronics Co., Ltd
Address: {36fc9e60-c465-11cf-8056-444553540000}\0009
Current State: Busy

UUID: a2c62c83-250d-4e3b-b2e8-bece3c941033
VendorId: 0x048d (048D)
ProductId: 0xc955 (C955)
Revision: 0.25 (0025)
Port: 4
USB version/speed: 2/Full
Manufacturer: ITE Tech. Inc.
Product: ITE Device(8295)
Address: {36fc9e60-c465-11cf-8056-444553540000}\0008
Current State: Busy

UUID: edea8ab3-45f7-476d-b989-1004a38877cd
VendorId: 0x048d (048D)
ProductId: 0xc100 (C100)
Revision: 16.0 (1600)
Port: 4
USB version/speed: 2/Full
Manufacturer: ITE Tech. Inc.
Product: ITE Device(8910)
Address: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0000
Current State: Busy

UUID: 441e42f6-ae80-450e-a4ec-48ae165b6d71
VendorId: 0x03f0 (03F0)
ProductId: 0x094a (094A)
Revision: 1.0 (0100)
Port: 1
USB version/speed: 2/Low
Manufacturer: PixArt
Product: HP USB Optical Mouse
Address: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0014
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"
Name: Kali Linux
Groups: /
Guest OS: Debian (64-bit)
UUID: b8b57d6f-3b31-4e2f-b949-4f52edab0caf
Config file: C:\Users\thijs\VirtualBox VMs\Kali Linux\Kali Linux.vbox
Snapshot folder: C:\Users\thijs\VirtualBox VMs\Kali Linux\Snapshots
Log folder: C:\Users\thijs\VirtualBox VMs\Kali Linux\Logs
Hardware UUID: b8b57d6f-3b31-4e2f-b949-4f52edab0caf
Memory size: 2048MB
Page Fusion: disabled
VRAM size: 128MB
CPU exec cap: 100%
HPET: disabled
CPUProfile: host
Chipset: piix3
Firmware: BIOS
Number of CPUs: 2
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: HardDisk
Boot Device 2: DVD
Boot Device 3: Not Assigned
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.: KVM
State: powered off (since 2021-07-04T11:48:53.442000000)
Graphics Controller: VMSVGA
Monitor count: 1
3D Acceleration: enabled
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): IDE
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
Storage Controller Name (1): SATA
Storage Controller Type (1): IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1): on
IDE (1, 0): Empty
SATA (0, 0): C:\Users\thijs\VirtualBox VMs\Kali Linux\Snapshots/{d0a900f7-95ca-4293-8a67-f0f15d951211}.vdi (UUID: d0a900f7-95ca-4293-8a67-f0f15d951211)
NIC 1: disabled
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 small
VendorId: 0bda
ProductId: a811
Revision:
Manufacturer:
Product:
Remote:
Serial Number:

Index: 1
Active: yes
Name: Realtek 802.11ac WLAN Adapter [0200]
VendorId: 0bda
ProductId: a811
Revision: 0200
Manufacturer: Realtek
Product: 802.11ac WLAN Adapter
Remote: 0
Serial Number: 00e04c000001

Bandwidth groups: <none>

Shared folders:<none>

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

Guest:

Configured memory balloon size: 0MB

Snapshots:

Name: Clean install - before proxychain try (UUID: 5de7179e-cce7-4338-b0d9-02242047d746)
Name: with metasploit (UUID: a970f50f-2cea-40cc-b2a9-5ebbc2da3fea)
Name: With metasploit again (UUID: bd7c4abe-bc37-49b9-8d3f-11bc28ff04af)
Name: With Nordvpn (UUID: ad7b6f0b-08f6-4095-a9f2-d5faa687c3c0)
Name: Metasploit updated (UUID: 6cb1f767-d608-4241-bcbe-dbd809372c99)
Name: Ipsweep + vuln scripts installed + gedit (UUID: 2588dce5-f192-4763-a3b6-9831f39e21a8)
Name: Apt get upgrade (UUID: c6f5cf8c-3ebd-4f06-a13a-1870f16f57a8)
Name: Terminal fix (UUID: e1aa2ecc-88e9-4f44-b72b-6ab995482d22)
Name: Terminal fix 2 (UUID: 371f675b-fbff-4e31-bc65-0f0ea6809abd)
Name: after lots sh files (UUID: fdedfe79-4330-4963-b6f0-7c93a0698102)
Name: before python3 install (UUID: 2f1df6ed-16af-4cf3-b29f-d29f3c4fe1f5)
Name: last msfupdate (UUID: fe90f9a8-9542-4945-acc9-2eed1084d4a3)
Name: before klooien met metaslpoit db (UUID: c0d00cad-6d53-4078-a8bd-0300681f2cc0)
Name: Before armitage install (UUID: 9a6d8202-e924-4623-87bc-fcc4f1edc416)
Name: WINE installation (UUID: 31fc71ca-93af-42e8-9f3a-1d521bcaf651)
Name: Before Burpsuite (UUID: 2a2e87c1-07a5-4779-919e-3776c91108c3)
Name: Strange ifconfig ip (UUID: a9238620-d94b-4e17-b344-d094cfb89dac)
Name: kali update en upgrade (UUID: 70b923c4-23b3-44bc-85d8-a1c7aadad9ff)
Name: Working config (UUID: 63bb7db6-0526-495b-abbd-08ebdb7dcc23) *
Attachments
VBoxSVC.zip
(3.23 KiB) Downloaded 2 times
Kali Linux-2021-07-04-14-00-21.zip
(31.99 KiB) Downloaded 3 times
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby scottgus1 » 4. Jul 2021, 15:00

The log shows the USB device being added:
00:00:57.898291 VUSB: Attached '0000000005e880f0[proxy 0bda:a811]' to port 1 on RootHub#0 (HighSpeed)

and I think, though I'm no Linux guru, that the output of 'lsusb' shows the device inside the VM OS.

However, you have two active USB filters for the same 0bda:a811 device. Disable the second filter named "Realtek 802.11ac WLAN Adapter [0200]" and try it again. Search the log for this line:
{timestamp} VUSB: Attached '0000000005e880f0[proxy 0bda:a811]' to port 1 on RootHub#0 (HighSpeed)

If you see it, and 'lsusb' still reports it, then the device is being passed into the VM, and it is up to the Kali network configuration to then try to use it.

Check with Kali's support channels on how to use the USB Wi-fi adapter.

One other piece of advice: that's a long list of snapshots. This makes the VM really delicate, and these snapshots aren't backups. Make a good copy of the Kali VM folder and any disk files residing outside the Kali folder, then you'll have the VM backed up. Also consider deleting some of the snapshots after the backup, to merge them and reduce the number of files that have to be open for the VM to run.
scottgus1
Site Moderator
 
Posts: 12471
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 12. Jul 2021, 12:42

Thnx again for your reply! Sorry it took a while to react. Busy week..

I've deleted the second USB filter and tried again, but no luck. ifconfig only gives:

root@kali:~# ifconfig
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

And Linux says no network devices available..

I will try the Kali linux forums next. Thnx for your help so far.

About the backup of the Kali vm

Make a good copy of the Kali VM folder and any disk files residing outside the Kali folder, then you'll have the VM backed up.


I've copied the folder: C:\Users\your user name\VirtualBox VMs\ Is that enough? i don't know if i have any disk files outside the Kali folder. How do i check this? Or should i use the export function?
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby scottgus1 » 12. Jul 2021, 16:30

Sceolan wrote: Busy week..

Aren't they always? :lol:

Sceolan wrote:I've copied the folder: C:\Users\your user name\VirtualBox VMs\ Is that enough?

Yes, assuming the Kali folder is somewhere inside "VirtualBox VMs".

To see where the VM's disks are located, open the VM's .vbox file (on Windows Hosts, Wordpad works well for viewing .vbox files) then look in the <HardDisks> section under <MediaRegistry> at the beginning of the file.
All the disk files will be listed there. If the base disk or any other disks are not in the VM's folder, then the path to the disk will start with a full driveletter:\path\to\diskfile.ext. Disks that are inside the VM's folder or in the Snapshots subfolder won't have the full drive letter path.

If lsusb still shows the USB device, then the device should be passed into the Kali OS, as far as I understand it. Confirm that lsusb still shows the Wi-Fi adapter, then maybe the Kali forums could help show how to enable it. Hope you get it going!
scottgus1
Site Moderator
 
Posts: 12471
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Bridged Networking not working with USB wifi adapter(s) - (Kali vm)

Postby Sceolan » 13. Jul 2021, 16:24

Thnx! One last question..

Vbox file says:

<MediaRegistry>
<HardDisks>
<HardDisk uuid="{0e97ab44-4f03-460d-92d3-5e71d696af07}" location="Kali Linux.vdi" format="VDI" type="Normal">

The rest there shows all the locations of the snapshots

So as i understand it we are good just copying the C:\Users\your user name\VirtualBox VMs\Kali Linux folder. Just doublechecking

and i also saw:

<DVDImages>
<Image uuid="{a67f5e91-3e3a-44d5-8c67-c630390fcb5c}" location="C:/Users/thijs/Desktop/kali-linux-2020.3-installer-amd64.iso"/>
</DVDImages>

That's the iso i used to install Kali. I don't need to backup that one as well right?
Sceolan
 
Posts: 7
Joined: 14. Jun 2021, 13:35


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 27 guests