Activated but Still No Internet in Zetland: the Feed Was in the DSL Port When It Needed the WAN Port (Superloop / Opticomm)

Student · ZetlandSuperloop 100MOpticomm buildingActivated, no internetDSL port vs WAN portOnline at 100 Mbps

A UTS student in Zetland had just had a Superloop connection set up — an Opticomm technician had come, configured the line, and the activation email had arrived. But the router still would not go online. When we arrived the phone line was in the router’s DSL port and the DSL light was on, so at first glance it looked correct. It wasn’t: this service needed an Ethernet feed into the WAN port, not the DSL port.

How we isolated it on-site

Checked the existing wiring and lights

DSL cable in DSL port, DSL light on

Tried to bring the connection up

Router stuck on “connecting”

Swapped in a known-good router

Same result → router not at fault

Called Superloop, did a guided video test

Advised: use the WAN port with Ethernet

Moved the feed to the WAN port and reconfigured

Online instantly, tested full 100 Mbps

Activated is not the same as connected

The account was genuinely active — the email was real and Superloop confirmed it on the phone. The problem was purely physical: which socket the feed was plugged into. Because the wall port was labelled “DSL” and the DSL light lit up, even the installer plugged it in that way. We only got there by changing one thing at a time and ruling the router out first.

Line in DSL port → router stuck “connecting”.
Second router, same wiring → still nothing, so it was not a dead router.
Superloop confirmed the service should run over Ethernet into the WAN port.
Feed moved to WAN, PPPoE re-entered → online, then WiFi name and password set.

DSL port vs WAN port · which one the line goes in

	Router DSL port	Router WAN port
Made for	A phone-line (DSL) service plugged in with a phone cable	An Ethernet feed from an NBN/Opticomm box or modem
Cable	RJ11 phone cable	RJ45 Ethernet cable
This home	Line was here — kept “connecting”	Moved here — online at once
Why the mix-up	The building has both a DSL phone line and an Opticomm fibre feed. The wall socket was labelled “DSL” and the router’s DSL light even came on, so the connection type looked right at a glance.

The lesson: a lit DSL light and a “DSL” label on the wall don’t prove the connection type. In buildings wired for both a phone line and Opticomm fibre, the Ethernet WAN port is often the correct feed. If a brand-new connection is activated but the router sits on “connecting”, try the other port before assuming the plan or hardware is broken.

Result

Root cause: the feed was in the router’s DSL port when this Superloop/Opticomm service needed an Ethernet feed in the WAN port — a mix-up even the installer made. Moving it to the WAN port and re-entering the login brought the line online at once, testing the full 100 Mbps.

Opticomm WAN/LAN swapped case Superloop guide TP-Link routers New connection not working Zetland service area

Activated but Still No Internet in Zetland: the Feed Was in the DSL Port When It Needed the WAN Port (Superloop / Opticomm)

Activated is not the same as connected

Related

Facing something similar?