How to Fix Kali Linux Internet Not Working: Reliable Troubleshooting Steps for 2026

Kali Linux internet issues usually come down to DNS, missing drivers, disabled network services, or virtualization misconfiguration.

This guide explains how to fix Kali Linux internet not working with clear checks that isolate the problem fast.

Check whether the problem is Wi-Fi, Ethernet, or DNS

Before changing settings, identify the failure point.

A connection can appear “down” even when only DNS is broken, or you may have a link but no route to the internet.

• No network icon or no IP address: likely interface, driver, or service issue.
• Connected to Wi-Fi but no websites load: often DNS or gateway routing.
• Ethernet works on other devices but not Kali: driver, link state, or NetworkManager problem.

Open a terminal and test the stack from bottom to top:

• ip a to confirm the interface exists and has an address.
• ip route to verify a default gateway is present.
• ping -c 3 8.8.8.8 to test raw connectivity.
• ping -c 3 google.com to test DNS resolution.

If IP ping works but domain ping fails, focus on DNS.

If both fail, focus on the interface, gateway, or driver.

Restart the network services

Kali uses NetworkManager on most desktop installs.

If it is stopped or misbehaving, the interface may never connect properly.

sudo systemctl status NetworkManager
sudo systemctl restart NetworkManager
sudo systemctl enable NetworkManager

If you are using a lightweight install or server-style setup, also check that the interface is not managed by conflicting tools.

Multiple network managers can interfere with each other.

Useful checks:

• nmcli device status
• nmcli connection show
• systemctl status networking

If NetworkManager shows the device as unavailable, the issue is usually below the connection layer, such as a missing firmware package or a blocked radio device.

Verify the wireless interface is not blocked

On laptops, Kali often loses connectivity because the Wi-Fi adapter is blocked by software or a hardware switch.

This is common after suspend, BIOS changes, or switching between operating systems.

rfkill list

If you see Soft blocked: yes or Hard blocked: yes, unblock it:

sudo rfkill unblock all

Then recheck the interface with ip a and nmcli device status.

If the adapter remains hard blocked, inspect the laptop’s physical wireless switch, airplane mode key, or BIOS settings.

Confirm the driver and firmware are installed

Kali Linux is Debian-based, so some wireless chipsets need extra firmware packages.

Missing firmware often causes the adapter to appear in the system without actually functioning.

Check kernel messages for hints:

dmesg | grep -i firmware
dmesg | grep -i wlan
dmesg | grep -i wifi

Look for messages such as “failed to load firmware” or “missing firmware.” Then install the appropriate package for your chipset.

Common examples include Intel, Realtek, and Broadcom firmware packages, but the exact package depends on your hardware.

You can also identify the device with:

lspci -nnk | grep -A3 -i network
lsusb

For USB Wi-Fi adapters, ensure the kernel module is loaded.

If the adapter is supported but the driver is absent, reinstalling kernel headers and firmware may help.

Check your IP address, gateway, and route

If the interface is up but the internet still fails, the routing table may be incomplete or incorrect.

This is especially common after switching networks or using static IP settings.

Inspect the configuration:

ip a
ip route

A healthy setup should show an IPv4 or IPv6 address on the active interface and a default route similar to default via 192.168.1.1 dev wlan0.

If no default route exists, renew the lease or reconnect the interface:

sudo dhclient -r
sudo dhclient

When using NetworkManager, toggling the connection off and back on can also refresh DHCP and routing:

nmcli networking off
nmcli networking on

Fix DNS problems

DNS failures are one of the most common reasons people search for how to fix Kali Linux internet not working.

The machine may reach the internet by IP address, yet domain names still fail.

Check the resolver configuration:

resolvectl status
cat /etc/resolv.conf

If DNS servers are missing, stale, or pointing to an unreachable source, set working servers manually through NetworkManager or temporarily edit the resolver setup.

Reliable public DNS options include Google DNS, Cloudflare DNS, and Quad9.

For a quick test, try:

ping -c 3 1.1.1.1
ping -c 3 cloudflare.com

If the first command works and the second fails, DNS is the problem.

In many cases, rebooting the router or reconnecting to Wi-Fi refreshes DNS settings pushed by DHCP.

Resolve VirtualBox or VMware networking issues

In a virtual machine, Kali internet problems are often caused by the virtual adapter mode rather than Kali itself.

Bridged, NAT, and host-only modes behave differently.

• NAT: easiest choice for general internet access.
• Bridged adapter: gives the VM a presence on the same LAN as the host.
• Host-only: does not provide external internet by itself.

If Kali is in VirtualBox, confirm the adapter is enabled and attached to NAT or bridged mode.

If in VMware, verify the virtual NIC is connected at power on.

Also check the host machine’s own internet connection, since the guest depends on it.

Inside the guest, run:

ip a
ip route
ping -c 3 8.8.8.8

If there is no virtual adapter, reinstall the guest additions or tools package where appropriate, then restart the VM.

Inspect firewall and proxy settings

A firewall rarely blocks basic outbound browsing on Kali by default, but custom rules can break connectivity.

If you use iptables, nftables, or a VPN client, review the active ruleset.

sudo iptables -L -n -v
sudo nft list ruleset

Proxy settings can also interfere with traffic in browsers and package managers.

Check environment variables and desktop proxy configuration:

• echo $http_proxy
• echo $https_proxy
• Desktop network proxy settings

If a proxy is set incorrectly, web pages and package downloads may fail while raw ping still works.

Refresh Kali package sources if only updates fail

Sometimes the internet is working, but apt cannot reach repositories.

That usually points to DNS, repository configuration, or time synchronization rather than a full network outage.

Check your repository list and update metadata:

sudo apt update

If you see “temporary failure resolving” or repository errors, revisit DNS.

If TLS errors appear, verify the system clock:

timedatectl status

An incorrect date can break secure connections to package mirrors and websites.

Enable time synchronization if needed:

sudo timedatectl set-ntp true

Use a practical recovery sequence

If you want the fastest path, try this order:

1. Confirm the interface exists with ip a.
2. Check whether it is blocked with rfkill list.
3. Restart NetworkManager.
4. Test IP connectivity with ping 8.8.8.8.
5. Test DNS with ping google.com.
6. Inspect the route with ip route.
7. Check firmware and driver messages in dmesg.
8. Review VM network mode if Kali is virtualized.

This sequence narrows the fault quickly and avoids random changes.

In most cases, the fix is one of three things: re-enabling the adapter, correcting DNS, or repairing the virtual network configuration.