# Installed kali linux 64bit on virtual meachine Having Trouble with wireless adapter **URL:** \ **Category:** Discussion & Solutions\ **Tags:** solved\ **Created:** [May 5, 2026, 9:16pm UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792 "2026-05-05T21:16:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![NOBITHEMADNESS](https://onehack.st/user_avatar/onehack.st/nobithemadness/32/173509_2.png) [@NOBITHEMADNESS](https://onehack.st/u/NOBITHEMADNESS)\ **Post date:** [May 5, 2026, 9:16pm UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/1 "2026-05-05T21:16:36Z")
how can i change my kali linux ip to 192 ip adress series instead od nat ip ![image](https://onehack.st/uploads/default/original/3X/8/f/8f1445060bf950635280e83fc4a1eae6087f56fb.jpeg) ---
**Author:** ![leonardo](https://onehack.st/letter_avatar_proxy/v4/letter/l/e56c9b/32.png) [@leonardo](https://onehack.st/u/leonardo)\ **Post date:** [May 6, 2026, 8:01am UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/2 "2026-05-06T08:01:50Z")
go to vm manager ( where you click start to run the linux)… then click settings … then select network … there you will see ‘attached to NAT’ change it to ‘bridge adapter’ then select ok . now restart the linux and check the ip ---
**Author:** ![NOBITHEMADNESS](https://onehack.st/user_avatar/onehack.st/nobithemadness/32/173509_2.png) [@NOBITHEMADNESS](https://onehack.st/u/NOBITHEMADNESS)\ **Post date:** [May 6, 2026, 8:41am UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/3 "2026-05-06T08:41:03Z")
Sir after changing bridge adaptor my ip on the kali linux is the same as before thats my problem could you please help me ![image](https://onehack.st/uploads/default/original/3X/f/8/f8c3761b003cdf22b4266173852ba3aaab75d6a4.png) ![image](https://onehack.st/uploads/default/original/3X/5/c/5cd689342e7ed23c24e046a77a78c13c8cbe4c37.jpeg) ---
**Author:** ![leonardo](https://onehack.st/letter_avatar_proxy/v4/letter/l/e56c9b/32.png) [@leonardo](https://onehack.st/u/leonardo)\ **Post date:** [May 6, 2026, 1:53pm UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/4 "2026-05-06T13:53:36Z")
sorry brother i know this much only … mine was fixed the way i told you to do … and one thing i know you must have done it but make sure after doing the changes you restart your kali linux. ---
**Author:** ![debian\_genie](https://onehack.st/user_avatar/onehack.st/debian_genie/32/168835_2.png) [@debian\_genie](https://onehack.st/u/debian_genie)\ **Post date:** [May 6, 2026, 11:01pm UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/5 "2026-05-06T23:01:16Z")
Hey I had a similar problem, chage here until it resolves ![f8c3761b003cdf22b4266173852ba3aaab75d6a4](https://onehack.st/uploads/default/original/3X/e/8/e8b3cb5b1747c66e1dd6ad29d8948a46285c1e31.png) From the adapter navigate to name and change it. ---
**Author:** ![NOBITHEMADNESS](https://onehack.st/user_avatar/onehack.st/nobithemadness/32/173509_2.png) [@NOBITHEMADNESS](https://onehack.st/u/NOBITHEMADNESS)\ **Post date:** [May 7, 2026, 2:24am UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/6 "2026-05-07T02:24:14Z")
but after switching to other adapters internet in kali linux is not working ---
**Author:** ![Prometheus](https://onehack.st/user_avatar/onehack.st/prometheus/32/34950_2.png) [@Prometheus](https://onehack.st/u/Prometheus)\ **Post date:** [July 30, 2026, 2:01pm UTC](https://onehack.st/t/installed-kali-linux-64bit-on-virtual-meachine-having-trouble-with-wireless-adapter/321792/7 "2026-07-30T14:01:25Z")
![Kali VM to a real 192.168 LAN IP](https://onehack.st/uploads/default/original/3X/d/9/d9c0067f3b18b89096b1ff60dfea4d0eeeebd3fa.jpeg) Your Kali is stuck on **10.0.2.15** because NAT hides it behind VirtualBox’s own private router. Switching to Bridged _should_ drop it onto your **192.168.x** — and here’s the real reason it didn’t: **over Wi-Fi, VirtualBox can’t truly bridge.** Wi-Fi cards have no “promiscuous mode,” so your router sees the VM’s second MAC address and quietly refuses it. That’s the whole bug. **Why your two attempts failed** (exactly what you saw): - 🔁 **Same IP after switching to Bridged** → you changed it with the VM _running_ (live network edits are ignored) **and** Kali kept its old NAT lease. Power off first, then renew the lease. - 🔌 **Lost internet after changing the “Name”** → you bound it to a dead Ethernet port. The Bridged **Name** has to be your **active Wi-Fi** card. Now pick the box that matches what you actually want 👇 ⚡ **Just want the IP to read 192.168.x + internet — 30 sec, can’t fail** On the **host** (not inside Kali), VM shut down: ```auto VBoxManage modifyvm "Kali" --natnet1 "192.168.55.0/24" ``` Swap `"Kali"` for your VM’s exact name → boot → `ip a` shows **192.168.55.x** , internet works, zero Wi-Fi drama. _Downside: still private — real LAN devices can’t see it._ 🌐 **Be a REAL device on your home LAN (reachable, can scan other devices)** — Bridged, done right 1. **Shut the VM fully down** (not paused). 2. Settings → Network → Adapter 1 → **Bridged Adapter** → **Name = your live Wi-Fi card**. ↳ Find it: Windows host → `ipconfig`, pick the adapter with a **Default Gateway**. Linux host → `ip route get 1.1.1.1`. 3. **Advanced** → Promiscuous Mode = **Allow All** · **Cable Connected ✔** · click the MAC-refresh icon. 4. Boot Kali, then force a fresh lease (don’t just reboot): ```auto sudo dhclient -r eth0 && sudo dhclient -v eth0 # or: sudo systemctl restart NetworkManager ``` 1. Check: `ip a` + `ip route` → **win = a 192.168.x address with a 192.168.x gateway.** Still on 10.0.2.15 or a 169.254.x? Your router is rejecting the VM’s MAC — stop fighting it, drop to the next box. ↓ 📶 **Bridged won’t lease over your Wi-Fi? Give Kali its OWN radio** — the reliable fix Pass a **USB Wi-Fi adapter** straight into the VM. Kali then joins the Wi-Fi _itself_ and pulls a real 192.168 lease from the router — no bridge involved _(bonus: this is also the only way to get **monitor mode** in a VM)_. - Install the **[VirtualBox Extension Pack](https://download.virtualbox.org/virtualbox/7.2.14/Oracle_VirtualBox_Extension_Pack-7.2.14.vbox-extpack)** — version **must match** your VBox (Help → About). - VM off → Settings → **USB** → enable + USB 2.0/3.0 → **＋** → pick the adapter (listed by chipset, e.g. _“Realtek 802.11ac”_). Leave **Remote = Any**. - Boot Kali → **Devices → USB → tick the adapter** → connect to your Wi-Fi. - Uses RTL8812AU / Alfa AWUS036ACH and no `wlan0` shows? → `sudo apt install realtek-rtl88xxau-dkms`, replug. _([driver](https://github.com/aircrack-ng/rtl8812au))_ 🧱 **Want a 192.168 that NEVER breaks (home lab, don’t need real LAN peers)** - **[NAT Network](https://www.virtualbox.org/manual/ch06.html#network_nat_service)** — Wi-Fi-proof, choose your own subnet: ```auto VBoxManage natnetwork add --netname natlan --network "192.168.15.0/24" --enable --dhcp on VBoxManage modifyvm "Kali" --nic1 natnetwork --nat-network1 natlan ``` - **[Host-Only + NAT](https://www.virtualbox.org/manual/ch06.html#network_hostonly)** (2 adapters) — a rock-solid **192.168.56.x** between host↔VM (SSH, Metasploit callbacks) _plus_ NAT for internet. Never touches Wi-Fi, never dies. 💡 **One trap:** a **static** 192.168 IP inside Kali only works _after_ the adapter **mode** already puts you on that subnet — set the mode first, the static IP second (else it routes nowhere). 🖥 On **VMware** instead? It bridges Wi-Fi far better — Virtual Network Editor → bind **VMnet0** to your Wi-Fi card _by name_, then tick **“Replicate physical network connection state.”** _NAT hides you. The LAN only lets in a MAC it trusts — so either wear one it knows, or bring your own radio._