Hey Daniel,

As someone who previously had a foot in the camp of Spark and now Voyager… I know this fault fairly well.

There is a feature in the mikrotiks that gets enabled with the app normally called “internet detection”. This turns on a DHCP client on the WAN connection.

May have changed since I left Spark, but last I checked, if you dial DHCP, it will come through as failed attempts and you will essentially go into the naughty bin for a little while – It’s an intended feature, but really hard to see in logs.

Kind regards,

Troy

Troy Baird | Senior Managed Service Engineer - Lead 0800 4 SPEED Troy.Baird@voyager.nz | voyager.nz

YOUR DIGITAL TRANSFORMATION PARTNER

From: Daniel Christie <Daniel@cloudland.co.nz>
Sent: Wednesday, 31 August 2022 11:22 am
To: nznog@list.waikato.ac.nz
Subject: [nznog] Mikrotik CPE with Spark Fibre issue

Hi,

I work for MSP and having issues with customers Mikrotik routers that connect specifically with Spark Fibre.

The issue is the routers when initially configured work well and run continuously for many day/weeks/months

But eventually something kicks the connection then the PPPoE on the Mikrotik will fail to re-establish its WAN fibre connection.

The solution has been to get customer to get their Spark provided router connected which works, then they swap the Mikrotik back in again and it works again.

I have done plenty of googling but can’t find anything helpful
We generally resell voyager fibre to most of our customers with the Mikrotik router and they work flawlessly, but some customers insist on staying with spark and we prefer to only deploy Mikrotiks

These logs rotate over and over while its down…

Can anyone (hopefully Spark engineer) please help with this?

Regards,

Daniel @ Cloudland