Two things made this job unusual, and neither of them was the fault itself. The router was a brand and model I had not come across on a job before, with an interface nothing like the ASUS and TP-Link units I see every week. And the plan was 25 Mbps — the slowest download speed I have been called out to in Sydney, on a fibre service, and not a bargain for what it delivers.
The service was already activated and the physical side was fine. The only thing standing between the student and a working connection was that the router had never been told how to connect — and the usual way of telling it, a web admin page, did not exist on this model.
| App-managed (this AmpliFi) | Typical web admin router | |
|---|---|---|
| How you configure | Official app on a phone | Browser page at the router's address |
| Needs a computer? | No — useful when there is none on site | Usually easier with one plugged in |
| If you have never seen it | Nothing looks familiar; reset and follow the prompts | Layouts differ but the fields are recognisable |
| Missing mesh units | App may expect nodes that are not present | Main router works standalone |
| What still has to be right | Connection type and account details | Connection type and account details |
Root cause: the router had never been configured for the service, and this AmpliFi has no conventional web admin page to configure it from. We reset the unit, followed its prompt to install the official app, set the connection type to PPPoE in the app and entered the broadband account details the student had been issued. The app reported the connection as up, and an on-site speed test matched the 25 Mbps plan — the absent mesh units turned out not to block the main unit from working on its own.
Call or message us — 90% of messages get a reply within an hour.
Call 0420 119 140 Send a Message