There Was No WiFi Name to Connect To: a Router Reset, Then the Wall Port Turned Out to Be UID2 (Optus FTTP, Sydney)

Student · SydneyOptus · FTTPTelstra routerNo WiFi name visibleWall port UID1 → UID2Remote support

This one started at the very beginning of the problem: not slow WiFi, not dropouts — there was no network name to tap at all. It was handled entirely over messages and photos, and it turned into two separate faults stacked on top of each other. The first one hid the router. The second one hid the internet.

Two faults stacked · where each one broke the chain

NBN wall port

UID1 dark

Broken here

→

Telstra router WAN

no link

→

Router WiFi (SSID)

not broadcast

Broken here

→

Your phone

nothing to join

Two independent problems produced one symptom. The SSID was missing because the router had been used before and left on a custom or hidden network name, so nothing appeared in the list. Separately, the Ethernet cable was in the wrong wall port — UID1, while the provider's activation email specified UID2, so the port light stayed dark and no service reached the router. Fixing only one of them would have left the student still offline.

Reset and restart are not lazy — they are how you rule things out

Resetting has a bad reputation because people reach for it randomly. Used deliberately it is one of the fastest tests available.

A factory reset returns the router to the network name printed on its label, so you immediately know whether the wireless hardware works.
If a full reset still produces no network at all, you have proved a hardware fault rather than guessing at one.
Do it knowing the cost: your connection settings and any custom WiFi name and password go with it, so have the provider's details to hand first.
In this case the reset answered the first question in under a minute — and immediately exposed the second, unrelated fault.

How it was solved over messages

Confirmed the symptom from photos: no WiFi name in the list at all

Not a password problem

Reset the router so it went back to its factory SSID

The network appeared and joined

Connected to the router but still no internet — checked the wall port light

UID1 light was not lit

Read the provider's activation email: the service was assigned to UID2, so we moved the cable

Port light came on normally

This FTTP service obtains its address automatically, so the router dialled on its own

Online after a short wait

The wall port detail is the part worth remembering, because it catches a lot of people in newer Sydney buildings.

A unit can have several network sockets, and typically only one of them carries your service.
The activation email from the provider usually states which one — here it was UID2, not the UID1 the cable was in.
The port indicator is the quickest confirmation: a dark light on the port you are using means the service is not there.
On an FTTP service that obtains its address automatically, you often do not need to configure anything — once the right port is used, it simply comes up.

Result

Root cause: two stacked faults. The router had been left on a custom network name so no WiFi appeared in the list, and the Ethernet cable was in wall port UID1 while the provider had assigned the service to UID2, leaving the port light dark. A factory reset restored the SSID, moving the cable to UID2 lit the port, and because this Optus FTTP service obtains its address automatically the connection came up shortly afterwards — all handled remotely.

Optus guide What is FTTP fibre Telstra guide Finding your NBN box New connection not working Router setup service

There Was No WiFi Name to Connect To: a Router Reset, Then the Wall Port Turned Out to Be UID2 (Optus FTTP, Sydney)

Reset and restart are not lazy — they are how you rule things out

How it was solved over messages

Related

Facing something similar?