Archive / Experiments / Oddities

Ethernet to Wi‑Fi,
Sideways

How a Wi‑Fi extender's Ethernet jack rescued a desktop from a stubborn 5 GHz adapter—and how a network repair casually turned into an operating-system upgrade.

Field notes · Home networking · Ubuntu · A practical workaround

Sometimes the elegant solution is not to persuade the troublesome component to behave. Sometimes it is to route around it, give the job to a different device, and let Ethernet do what Ethernet has been doing for decades: quietly carry the bits without making a scene.

This experiment began with an Ubuntu desktop whose Realtek RTL8821AE wireless adapter could see the 5 GHz world in theory, but whose Linux-side channel/regulatory situation made that path troublesome. Rather than spend the evening wrestling the driver, we used a Wi‑Fi extender that already had a working relationship with the existing network.

The idea: let the extender handle the wireless connection to the router, then connect the desktop to the extender's Ethernet port. The desktop sees a normal wired network interface; the extender quietly does the wireless part.

01 / The topology

Network topology after the workaround The Linksys router connects wirelessly to a Wi-Fi extender using the NEO 5 GHz network. The extender connects by Ethernet to the ASUS desktop. The desktop receives a LAN address from the main router. Linksys router NEO / NEO_5GHz Gateway: 192.168.1.1 5 GHz Wi‑Fi Wi‑Fi extender Wireless upstream Ethernet LAN port Ethernet ASUS desktop Wired interface 192.168.1.181 The desktop's Realtek Wi‑Fi adapter is bypassed, not repaired. The existing NEO network remains the upstream network.
Resulting arrangement, simplified. The extender is the wireless client/bridge in the middle; the desktop uses Ethernet. The measured LAN address was assigned on the existing NEO network.

02 / The setup, without the ceremony

  1. Open the extender's management page from a phone. The label suggested 192.168.11.1; during discovery it appeared on the existing LAN as 192.168.1.122.
  2. Use the extender's setup scan and select NEO_5GHz, then choose the 5 GHz option.
  3. Enter the existing NEO wireless password, save, and let the extender reboot.
  4. Connect the ASUS desktop's Ethernet port to the extender's LAN/Ethernet port.
  5. Confirm the desktop gets a normal LAN address and test connectivity.

No new upstream network was introduced. The extender stayed on NEO; the desktop did not need to win an argument with its own Wi‑Fi driver.

03 / The numbers: before and after

Short ping tests to a public IP address showed a clear improvement after the new arrangement. These are small samples, not a guarantee of permanent performance—but they are a useful snapshot of the change.

TestPacket lossAverage round tripMaximum
Before, 1.1.1.1 (4 packets)25% (3/4 replies)192.8 ms358 ms
After, 1.1.1.1 (10 packets)0% (10/10 replies)41.582 ms55.864 ms
After, google.com (4 packets)0% (4/4 replies)25.079 msNot recorded
Before25% lossOne of four packets disappeared.
After0% lossTen of ten packets returned.
After average41.6 msTo 1.1.1.1, in this short test.

04 / What the 351 Mbps figure does—and doesn't—say

The gateway connected to the extender reported a 351 Mbps link rate at 5.2 GHz. That is a promising sign that the client-to-extender wireless link was using 5 GHz and negotiating a strong connection. It is not an internet speed test, and it does not independently prove the exact band or rate of the extender's own connection back to the Linksys router.

The extender was configured to use NEO_5GHz as its upstream network, so 5 GHz backhaul was the intended setup. We simply did not capture a separate status page that independently confirmed the extender-to-router link after reboot.

05 / The collateral upgrade

While we were at it… the Gateway was upgraded to Ubuntu 26.04.1 LTS. Because apparently a network experiment is also an acceptable time to renovate the building's operating system. 😏

The upgrade is part of the story, but it should not be confused with the cause of the improved ping results. The practical networking change was the extender's wireless connection to NEO paired with Ethernet from the extender to the ASUS desktop. The OS upgrade happened alongside the experiment; the tests recorded here do not isolate its effect.

06 / Why this workaround works

A Wi‑Fi extender with an Ethernet port can often provide a wired connection to a device that has no useful wireless path of its own. The extender handles the radio connection; the connected computer sends ordinary Ethernet frames to it. Depending on the extender's operating mode, it may act as a wireless bridge or use a repeater/NAT arrangement, so the exact network behavior varies by model.

In this setup, the ASUS received 192.168.1.181 and used the Linksys gateway at 192.168.1.1. That is consistent with the desktop joining the existing LAN through the extender, rather than being placed on an unrelated network.

Important distinction: the RTL8821AE driver was not fixed. Its wireless path was bypassed. This is a useful engineering move, not a driver diagnosis.

07 / Reusable field recipe

08 / Verdict

The experiment turned an unreliable wireless route into a working Ethernet connection by delegating the wireless job to a device already designed to do it. The short post-change tests showed zero packet loss and substantially lower latency than the initial sample. That's a successful practical outcome—even while leaving the original Realtek driver mystery available for a future episode.

Sometimes troubleshooting means finding the broken part. Sometimes it means finding a route that no longer needs it.


Experiment notes: Linksys WRT1900AC · existing NEO / NEO_5GHz network · generic Wi‑Fi extender with Ethernet port · ASUS desktop on Ethernet · Ubuntu 26.04.1 LTS on the Gateway.

Measurements are short samples from this specific setup and may vary with signal conditions, interference, routing, and time of day.

← Return to Oddities