How to Fix Wi-Fi Drops and Slow Speeds on elementary OS
A wireless connection that repeatedly disconnects or crawls on elementary OS can be caused by several different layers. The problem may sit in the laptop’s Wi-Fi driver, NetworkManager, router settings, radio interference, or the broadband service itself. Treating every fault as a DNS problem usually wastes time, while replacing hardware before checking basic diagnostics can be equally unnecessary.
Australian users also face a few common local conditions. NBN connections can deliver excellent speed to the router while a crowded apartment in Melbourne or Sydney limits the wireless link inside the home. Telstra, Optus and Aussie Broadband customers may use different modem firmware and support settings, and older routers supplied with an internet plan may struggle with busy 5 GHz networks or many connected devices.
Establish whether the fault is local
Begin by checking whether the connection drops only on the elementary OS computer. Test a phone or another laptop from the same room, then compare the result beside the router. If every device disconnects, the likely causes include the NBN service, modem, router, or an upstream outage. If only elementary OS is affected, focus on the computer’s driver, wireless profile, power management, and signal quality.
A simple speed test can separate internet performance from wireless performance. First, run a test close to the router, then repeat it from the normal workspace. A large difference suggests weak signal or interference. A consistently low result on every device may indicate a congested local exchange, a router limitation, or a problem with the broadband plan rather than elementary OS.
When the connection fails, note whether the Wi-Fi icon disappears, the network remains listed but refuses authentication, or the connection stays active while websites stop loading. These symptoms point in different directions. A missing interface suggests a driver or hardware issue; repeated password prompts often indicate authentication or saved-profile trouble; an active connection with failed browsing may involve DNS or the router’s internet link.
Check the adapter, firmware and network state
Open Terminal and identify the wireless hardware with:
lspci -nnk | grep -A3 -i network
For a USB adapter, use lsusb instead. The output should show the chipset and the kernel driver currently attached to it. Intel adapters commonly work well with the in-kernel iwlwifi driver, while some Realtek and MediaTek models depend more heavily on the kernel version and installed firmware. Do not download a random driver script from a forum before identifying the chipset.
Update elementary OS through AppCenter and install all available system updates. Firmware packages are often delivered through the normal update process, and a newer kernel can resolve disconnects caused by an older driver. Restart after updates rather than assuming that the new firmware is already in use. You can inspect recent kernel messages with:
journalctl -k -b | grep -iE 'wifi|wlan|firmware|iwlwifi|rtl|mt76'
Look for messages about firmware failures, authentication timeouts, repeated resets, or the interface being renamed. A message that appears once during startup is less important than an error repeating each time the connection drops.
NetworkManager can also reveal its view of the connection:
nmcli device status
nmcli connection show
If the Wi-Fi device is listed as unavailable, check the hardware and software radio switches. If it is disconnected, the adapter is present but not associated. The command rfkill list shows whether airplane mode or a physical switch has blocked the radio. Unblock it with sudo rfkill unblock wifi when appropriate.
Improve signal quality and router compatibility
Wireless speed depends on signal strength, channel congestion, antenna quality and the capabilities shared by both ends of the connection. A laptop in a back bedroom may connect successfully but negotiate a very low rate. Concrete walls, metal shelving, cordless devices and neighbouring access points can all reduce performance. In an Australian unit block, dozens of nearby networks may compete for the same 2.4 GHz channels.
Use the elementary OS network menu to try both the 2.4 GHz and 5 GHz networks if your router presents separate names. The 2.4 GHz band travels farther and penetrates walls better, but it is commonly crowded. The 5 GHz band can be much faster at short range, although some channels are affected by radar detection and may briefly disappear when the router changes channel.
Log in to the router and select a fixed, reasonably clear channel rather than leaving an older automatic setting to make frequent changes. For 2.4 GHz, channels 1, 6 and 11 are generally the practical choices. On 5 GHz, avoid forcing a DFS channel while troubleshooting, particularly if the laptop disconnects whenever the router detects radar activity. Keep the router in an open, central position rather than inside a cabinet or behind a television.
Check the router’s wireless mode as well. Very old compatibility modes can reduce throughput, while unusual combinations of WPA settings may cause authentication loops. WPA2-Personal with AES is a useful baseline for testing. If the router offers WPA3 transition mode and elementary OS repeatedly fails to reconnect, temporarily test WPA2 alone, then restore a stronger modern configuration once the cause is clear.
Compare common fixes with likely causes
Several fixes are regularly recommended for wireless problems, but they address different symptoms. Applying all of them at once makes it difficult to know what actually worked. Change one setting, test for a while, and record the result. A connection that survives a short speed test may still fail during a long video call or a large download.
| Symptom | Likely cause | Useful test or fix |
|---|---|---|
| Wi-Fi vanishes from the panel | Driver, firmware, hardware switch or kernel issue | Check rfkill, kernel logs and available updates |
| Network disconnects after idle periods | Wireless power management | Disable power saving temporarily and compare |
| Strong signal but slow browsing | DNS, router load or broadband issue | Test another DNS resolver and compare other devices |
| Fast connection beside router only | Weak signal or interference | Change band, router position or wireless channel |
| Repeated password prompts | Saved profile or security mismatch | Forget the network and recreate it |
| Drops on 5 GHz only | DFS channel or band compatibility | Test a non-DFS channel or 2.4 GHz |
| All household devices are slow | Router, NBN service or provider issue | Test by Ethernet and check provider status |
For a saved profile problem, open the network settings, remove the connection, and join it again. You can also use NetworkManager from Terminal, but the graphical route is safer for beginners. Re-enter the password carefully and avoid copying trailing spaces from a password manager.
When the signal is strong but only domain names fail, test DNS separately. ping 1.1.1.1 checks basic reachability without looking up a hostname, while ping example.com also depends on DNS. A DNS change cannot repair a weak radio link, though it can make browsing feel slow when the resolver supplied by the router is unreliable.
Test power management and reconnect behaviour
Laptop power management can put the wireless adapter into a low-power state that some drivers handle poorly. This is especially noticeable after suspending the computer, moving between networks, or leaving it idle. First identify the active connection name:
nmcli -t -f NAME,TYPE connection show --active
Then disable Wi-Fi power saving for that profile:
nmcli connection modify "Your Wi-Fi Name" 802-11-wireless.powersave 2
nmcli connection down "Your Wi-Fi Name"
nmcli connection up "Your Wi-Fi Name"
Replace the quoted name with the exact profile name. The setting applies to that connection, so a different network may continue using its own power policy. To reverse it, use 802-11-wireless.powersave 1, which returns control to the default behaviour.
You can also perform a short, temporary test with iw. First find the interface name using iw dev; it is often something such as wlp2s0. Then run:
sudo iw dev wlp2s0 set power_save off
This change may be lost after reboot, which is useful during diagnosis. If the drops stop, power management is a strong suspect. The trade-off is battery life, so consider leaving it disabled only if the stability improvement is worth the extra consumption.
After suspend, NetworkManager may fail to restore the association even though the adapter is visible. Disconnecting and reconnecting from the panel is a harmless first step. If this happens consistently, install system updates and inspect the logs from the current boot and the previous boot with journalctl -b -1. Avoid repeatedly restarting NetworkManager while a video call or file transfer is running, since it will interrupt every active network session.
Rebuild the connection and inspect interference
A damaged or outdated NetworkManager profile can preserve an incorrect BSSID, band preference, or security option. In the network settings, forget the affected network and create it again. This removes old credentials and connection-specific choices while leaving other networks untouched. It is often more effective than changing the router password when the router itself works normally.
For a more detailed view of nearby access points, run:
nmcli device wifi list
Pay attention to signal percentage, channel and security type. Several networks using the same 2.4 GHz channel can explain poor performance even when your own signal looks strong. A Wi-Fi analyser app on an Android phone can provide a visual survey, but the elementary OS command gives enough information for many cases.
Australia has its own radio regulatory settings, and the router should be configured for the Australian region rather than imported settings. Linux normally obtains the correct regulatory information through the kernel and firmware, but a manually altered system can behave oddly. Check the current setting with iw reg get. Do not force a country code casually: incorrect regulatory settings can make channels unavailable or lead to unlawful transmission behaviour under ACMA rules.
If a USB adapter is being used, test a different USB port and keep it away from USB 3 devices, hubs and external hard drives. Some combinations produce radio interference, particularly on 2.4 GHz. A short USB extension cable can move the adapter away from the computer’s metal chassis and nearby cables, which is a simple test before buying replacement hardware.
Separate internet speed from Wi-Fi speed
A wired test is the clearest way to identify where performance is being lost. If possible, connect the computer to the router with Ethernet and run several tests at different times. Ethernet speed close to the plan’s advertised rate, combined with poor Wi-Fi, points towards wireless configuration or placement. Slow Ethernet as well suggests the NBN connection, router, provider, or a broader service issue.
Remember that speed-test results vary with server selection, network load and the test device. Run more than one test and compare latency, download speed and upload speed. A high download result does not rule out packet loss, which can make SSH sessions, online games and video meetings unstable. An extended ping to the router can reveal local packet loss:
ping -c 50 192.168.1.1
Use your router’s actual gateway address if it differs. Packet loss or large latency spikes to the gateway indicate a local wireless issue. Clean replies to the gateway but poor replies beyond it point towards the router’s internet connection or the ISP.
For an NBN household, compare the result with another device over Ethernet or close-range Wi-Fi. Contact the provider when all devices show the same fault, especially if the modem’s WAN light changes, the connection drops at regular times, or the issue follows a known outage. Support staff may ask for the modem model, outage timestamps and wired test results, so keeping those details can shorten the exchange with Telstra, Optus or an independent provider.
Keep a stable setup and protect your privacy
Once the connection is reliable, avoid changing several router and desktop settings without a reason. Keep elementary OS, the kernel, firmware and router software current. Use a clear network name, a strong password and modern encryption. Save a note of the working band and channel so that a future router reset does not send you back to trial and error.
If troubleshooting involves network diagnostics, remember that logs can contain network names, device identifiers and local addresses. Remove those details before posting output in a forum. Elementary OS users who want to review broader system choices can also read this privacy settings guide, particularly when deciding which diagnostic information to share.
A reliable fix should survive normal use: suspend and resume, a large download, a video call, and movement between rooms. If disabling power saving solves the issue, accept the battery trade-off knowingly. If a router channel change helps, leave automatic channel selection off only when it remains stable. If a replacement adapter is needed, choose one with well-supported Linux firmware instead of relying solely on a low price or Windows compatibility label.
The most useful habit is to work from evidence. Check whether other devices are affected, identify the adapter and driver, inspect signal and channel conditions, compare Ethernet with Wi-Fi, and change one variable at a time. On elementary OS, persistent wireless drops are often fixable through updates, a clean network profile, better router placement, a non-congested band, or a carefully tested power setting. What the reader should remember is that stable Wi-Fi comes from locating the failing layer first, then applying the smallest change that addresses it.
