-kali-network-recovery-example-

Kali / Metasploit Lab Network Recovery (VirtualBox + Windows)

A practical troubleshooting guide to fix the common issue where Kali Linux (VirtualBox) shows Wi-Fi/NAT connected but no internet after pentesting labs (e.g., Metasploit, pivoting, proxying, MITM tooling).

This repo documents a real-world fix path:

• Kali VM routes look correct
• But ping 8.8.8.8 fails with errors like “Destination Net Unreachable”
• Windows host shows No Internet / No DHCP server found
• Solution: restore host DHCP/network stack + confirm VirtualBox NAT

Ethical use only: home labs, training VMs, authorized environments.

---

Symptoms

In Kali (VirtualBox)

• Network interface has IP (e.g., 10.0.2.15/24)
• ip route shows default route (e.g., default via 10.0.2.2 dev eth0)
• But:
  • ping 8.8.8.8 fails
  • DNS lookups fail
  • Browser shows no internet

On Windows Host

• Taskbar shows globe icon (no internet)
• Windows troubleshooter reports:
  • “No DHCP server was found.”

---

Root Cause (Most Common)

VirtualBox NAT depends on the Windows host’s internet connection.

If the Windows host:

• is not receiving a DHCP lease,
• has broken network stack (Winsock),
• has VPN/proxy conflicts,
• or has adapter issues,

then the VM NAT gateway (10.0.2.2) cannot reach the internet.

---

Quick Verification

Run inside Kali:

ip a
ip route
ping -c 4 8.8.8.8
ping -c 4 google.com