The Broadband Account Belonged to a Flatmate Two Tenants Ago: Recovering a PPPoE Login After the Old Router Walked Out the Door (Exetel 250M, Zetland)

The flat had a working Exetel service on a 250 Mbps plan and a wall socket that had been carrying it for a long time. The tenant had a perfectly good Redmi router he had brought over from China. Plug the two together and nothing happens — which is the specific frustration of this fault, because every physical thing you can point at is fine.

The history is what explains it. The service had been ordered by tenant A. When A left, it passed to tenant B, and A's original router stayed in the flat and kept working, so nobody had reason to think about the account behind it. Then B moved out and took that router with him. The current tenant connected his own, and the connection that had run continuously through two changes of occupant stopped — on the same line, at the same socket, with the same provider and the same plan.

Plenty of people swap routers in an Australian rental and never hit this. The difference is how the service authenticates. If the connection uses an automatically assigned address, the network does not ask the router to identify itself: plug in a new one, and it works within a minute. If the connection uses PPPoE — a dial-up style login over the WAN port — then every router has to present a username and password before the service will carry any traffic. This flat was on PPPoE.

That credential is issued once, when the account is opened, and it lives in two places: the activation email in the account holder's inbox, and the configuration stored inside whichever router was set up with it. In this flat both of those had walked out the door with people. The account holder's inbox was two tenants away and the configured router was in a box somewhere with tenant B. Neither of those is a technical problem, which is why no amount of resetting, re-cabling or testing would have produced an inch of progress. The fastest thing we could do on site was establish that the fault was informational rather than physical, and then stop touching hardware.

From there it stopped being a networking job. The current tenant did not have the details and could not reasonably be expected to. The previous flatmate was reachable but was out; we waited on site until he was back, which is not glamorous work but was the only thing on the critical path. He filled in the history and put us in contact with the original account holder, who went and looked through her email and sent the details across without much fuss. Entered into the Redmi router, the connection came straight up.

It is worth being explicit about what made this end well, because it very nearly does not have to. Two former flatmates, one of them two tenants back, both still contactable and both willing to help with something that no longer had anything to do with them. In previous jobs like this the chain has only ever been one person long. Take one of those links away — a phone number that no longer works, a person who does not reply — and the remaining option is to stop trying to recover the old service and open a new one in the current tenant's own name.

There was a second route we could not use here. The credential is stored inside the router that was originally configured with it, and if that unit has not been factory reset, the details can usually be read back out of its admin page. Flatmate B had that router, but not with him. Worth knowing for anyone in the same position: before the person who set up the broadband hands over or moves out, log in to the router and write the connection settings down.

Once the connection was up the rest was ordinary work. We moved the router to a better position for the way the tenant actually uses the flat, set the WiFi name and password to what he wanted rather than leaving whatever a previous occupant had chosen, and ran speed tests, which came in where he expected them for the plan.

The part worth carrying forward is not technical at all. When you move into a share flat with internet already running, ask two questions on day one: whose name is the account in, and does the connection use an automatic address or a login. If it is a login and the account belongs to somebody who is leaving, get the username and password written down before they go. It costs five minutes at a point when everyone is still talking to each other, and it removes the entire situation described above.