Skip to content
Sydney WiFi & Computer RepairSydney WiFi
Case Studies / Latest Case

Living-Room Wall Ethernet Port Activated for a Gaming PC in a Sydney CBD Apartment (Occom)

Student · Sydney CBDOccom planASUS routerWall Ethernet portGaming PC wiredPing ~5 ms in game

A student in a Sydney CBD apartment (the Greenland building) on an Occom plan wanted one thing: the gaming desktop in the living room running off the living-room wall Ethernet port instead of WiFi, to cut latency. The catch with wall ports is that they come in pairs — one socket near the router, one across the home — and nothing tells you which feeds which. We tested the router-side ports first, matched the right pair with two cables, wired the desktop, and watched the game hold a ~5 ms ping for five minutes straight.

How we matched the port on-site
1
Tested the router’s two spare LAN ports with a laptop
Both ports confirmed live
2
Cabled both ends at once to match the wall-port pair
Living-room port identified
3
Wired the gaming desktop to the wall port
Speed test passed on the spot
4
Five minutes of live gameplay at the desk
Ping held at ~5 ms
Matching a wall port is a two-cable job. One cable links the socket at the router end; the other links the far socket to a test laptop. Only with both ends connected at the same time can you confirm which pair is which — and whether the in-wall run actually works.

Why a gaming desk wants the wall port, not WiFi

WiFi vs wall-port wired · for a fixed gaming desk
WiFiWall-port wired
In-game pingFluctuates with interference and load~5 ms and flat in this flat
StabilityShares airtime with every phone and laptopA dedicated in-wall run to the router
InterferenceWalls, microwaves, neighbours’ WiFiNone on a cable
Best forPhones, tablets, sofa laptopsA desktop that never moves
For raw download speed, modern WiFi is usually fine. Latency is a different story: wireless airtime is shared, and one busy device or a noisy neighbouring channel shows up as ping spikes right when a fight starts. A wall port is a fixed cable run back to the router — this desktop stopped competing with every phone in the flat, and the player felt it in the first game.

Same afternoon, another flat: every wall socket dead

Where that second job stopped · the weakest link
Street line
ISP to test
→
In-wall cabling
dead
Bottleneck
→
Wall sockets ×3
no sync
→
DSL light, 2 routers
never lit

We tested three sockets and two different routers — the student’s TP-Link and our own unit — and no DSL light ever came on. That pattern puts the fault inside the walls, not in the gear: one for the ISP’s technician to re-terminate.

The second visit that afternoon was the opposite story: an urgent call-out where the student had already tried their own TP-Link on the socket and got no DSL light. We repeated the test with our router, then worked through the other two sockets in the flat — nothing would sync. That is as far as private gear can take it: when every socket is dead on known-good hardware, the line inside the walls or upstream needs the provider’s technician. We left the student with exactly what to tell the ISP so the booking lands on the right team.
Result

Two jobs, one afternoon. Job one: the living-room wall port was matched and the gaming desktop went wired — ~5 ms in-game ping, stable across a five-minute live test, no more WiFi in the path. Job two: three dead sockets on two routers proved the fault was in-wall, and the student left with a precise fault description for the ISP technician booking.

Related

Facing something similar?

Call or message us — 90% of messages get a reply within an hour.

Call 0420 119 140 Send a Message