Introduction
While setting up my homelab on Ubuntu Server, I encountered a Wi-Fi connectivity issue with a USB Realtek RTL8188EUS adapter.
The interesting part was that the hardware appeared to be functioning correctly at the lower layers:
- USB adapter was detected
- Kernel driver was loaded
- Firmware was present and initialized
- Wireless interface existed
But the server still couldn't establish a working Wi-Fi connection.
This troubleshooting session turned into an investigation of Ubuntu's networking stack, specifically the interaction between Netplan-generated services, wpa_supplicant, systemd, and wireless authentication.
A detected adapter and a loaded driver don't necessarily mean the networking stack is operational.
1. Environment
| Component | Details |
|---|---|
| Machine | Lenovo ThinkCentre M710q Tiny |
| OS | Ubuntu Server 26.04 LTS |
| Kernel | 7.0.0-30-generic |
| Wi-Fi adapter | USB Realtek RTL8188EUS |
| USB ID | 0bda:8179 |
| Kernel driver | rtl8xxxu |
| Firmware | RTL8188EU firmware, revision 28.0 |
| Network configuration | Netplan |
| Network backend | systemd-networkd |
| WPA authentication | wpa_supplicant |
The wireless interface was:
wlx001f05825cf5
2. Initial investigation — verify hardware and driver
The first step was to establish whether this was a USB detection, driver, or firmware issue.
Check USB device detection
lsusb
The Realtek adapter appeared with USB ID:
0bda:8179
Inspect kernel messages
sudo journalctl -k -b --no-pager -l
For targeted driver-related logs:
sudo journalctl -k -b --no-pager -l -g 'rtl8xxxu'
Verify the wireless interface
iw dev
At this point, the adapter was detected and the wireless interface existed.
The kernel was using:
rtl8xxxu
This was important because it moved the investigation beyond basic hardware detection.
3. Inspect the networking layer
The system was using Netplan to configure networking, with systemd-networkd managing the network configuration.
The wireless interface was not successfully establishing connectivity.
The next part of the investigation focused on the WPA supplicant service.
Check wpa_supplicant
wpa_supplicant -v
The installed version was:
v2.11
The system also had a global wpa_supplicant service running in D-Bus mode. However, the Netplan-generated per-interface WPA service was a separate component of the connection path.
This distinction mattered: the existence of a running global service did not establish that the interface-specific WPA configuration was working.
4. The service failure
During troubleshooting, the Netplan-generated WPA service for the wireless interface failed.
The service was:
netplan-wpa-wlx001f05825cf5.service
The failure reported:
203/EXEC
The logs also indicated that the generated service was unable to execute the configured WPA supplicant command.
The binary path was investigated.
ls -l /sbin/wpa_supplicant
ls -l /usr/sbin/wpa_supplicant
The /sbin path was not an independent missing directory; it resolved through the system's /usr merge.
The binary itself could be executed and returned its version.
Therefore, I did not conclude that the adapter's kernel driver was the root cause.
The exact underlying reason for the original 203/EXEC failure was not conclusively isolated. I treated it as a service execution/configuration failure based on the observed logs rather than claiming a confirmed systemd or Ubuntu bug.
5. Missing packages
During the investigation, the system was missing required packages for the WPA authentication workflow.
Because the homelab server initially had no internet connectivity, I used an offline package installation workflow:
- Downloaded the required Debian packages on macOS.
- Transferred them using a USB drive.
- Mounted the USB drive on Ubuntu.
- Installed the packages locally.
The packages installed were:
wpasupplicantlibpcsclite1
The package files used in the offline transfer were:
wpasupplicant_2.11-0ubuntu5_amd64.deb
libpcsclite1_2.4.1-1_amd64.deb
Install the packages
After mounting the USB drive and navigating to the directory containing the packages:
sudo dpkg -i ./libpcsclite1_2.4.1-1_amd64.deb
sudo dpkg -i ./wpasupplicant_2.11-0ubuntu5_amd64.deb
Verify the installation
wpa_supplicant -v
The binary was available and returned version 2.11.
6. Regenerate Netplan configuration
After resolving the package availability issue, I regenerated the Netplan configuration.
sudo netplan generate
The command completed without errors.
This step regenerates the configuration and service definitions based on the current Netplan configuration.
7. Restart the interface-specific WPA service
Rather than restarting unrelated services, I targeted the generated WPA service associated with the wireless interface.
sudo systemctl restart netplan-wpa-wlx001f05825cf5.service
After the restart, the service was running.
The logs showed successful WPA authentication and key negotiation, including:
WPA: Key negotiation completed
and:
CTRL-EVENT-CONNECTED
This was the first clear confirmation that the wireless connection was successfully established.
8. Validate connectivity
After WPA authentication completed, the wireless interface obtained an IP address via DHCP.
I verified connectivity with:
ip -br addr
Then tested external reachability:
ping -c 4 8.8.8.8
The ping succeeded.
SSH was subsequently used to connect to the server remotely from my Mac.
At this point, the homelab server was online and reachable.
9. Troubleshooting summary
| Layer | Observation | Status |
|---|---|---|
| USB | Adapter detected | Working |
| Kernel |
rtl8xxxu loaded |
Working |
| Firmware | Initialized | Working |
| Interface | Wireless device present | Working |
| WPA service | Interface-specific service initially failed | Failure observed |
| Package availability | Required packages were missing | Corrected |
| Netplan | Configuration regenerated | Completed |
| WPA | Key negotiation completed | Working |
| DHCP | Address obtained | Working |
| Internet | Ping succeeded | Working |
| SSH | Remote connection succeeded | Working |
10. What I learned
This was a useful reminder that Linux networking is layered.
When a wireless adapter is detected, it only confirms that the hardware and parts of the driver stack are operational. Connectivity still depends on several other components:
- Interface configuration
- Network manager/backend behavior
- WPA supplicant execution
- Authentication
- DHCP
- Routing and DNS
Troubleshooting is much more effective when each layer is verified before moving to the next.
I initially had a USB Wi-Fi adapter that appeared to be a hardware problem. The evidence pointed elsewhere.
11. Root cause caveat
The observed failure was associated with the Netplan-generated, interface-specific WPA service reporting 203/EXEC.
The connection was restored after installing the missing packages, regenerating Netplan, and restarting that service.
However, the precise trigger behind the original execution failure was not conclusively identified. This write-up documents the observed behavior and successful recovery procedure, not a confirmed Ubuntu defect.
Conclusion
The homelab is now online, and remote SSH administration is working.
More importantly, this incident reinforced a troubleshooting habit I want to continue applying:
Don't assume the failing component is the one that looks suspicious. Trace the failure across the stack and let the evidence guide the next step.
I'll be documenting more of these homelab incidents as I build out the environment.
Top comments (0)