I have a long-lasting issue with "Detect internet" status. It doesn't work after reboot, until I change and revert (even without pressing 'apply' button) any of lists in "Detect internet" dialog box.
After this manipulation "Detect internet" status works fine until next reboot.
Here's a small video (less than a minute) about this issue:https://youtu.be/kk6nRWx74yY
Is there any idea what happens?

currently workaround I have to use is to have a script in startup scheduler with this code:

Hi,

I have the same issue...and MT knows about it....

The only issue with detect internet is that you're using it.

+1000

Have a little faith, maybe they finally found some good use for it.In that case, please visitWhat is Detect Internet for?and share what exactly it is and how it makes your lives better. I'm genuinely interested.

Hi,

do you use mobile app? Once is internet detected you can see on the main menu how much trafic is used...

Make a feature request so that the app doesn't rely on detect internet.
Yes I use it from time to time, but I'm not using it to stare at the main screen watching the bandwidth usage.

[…] maybe they finally found some good use for it.In that case, please visitWhat is Detect Internet for?and share what exactly it is and how it makes your lives better […]

Honestly, if the "internet" label is not removed or hidden on the device, I have not found any such idiotic customer ...

Well, to satisfy mobile app without messing up interface lists the best config is, as I understand:

> /interface/detect-internet/ print
detect-interface-list: WAN
lan-interface-list: none
wan-interface-list: none
internet-interface-list: none

This detect-internet failure is still happening, in 7.8 -- any updates on when Mikrotik may fix this failure?

The only issue with detect internet is that you're using it.

This is a rather pointless feature and should be removed.

Unless you use the mobile app, in which case it's needed and useful to show nice visualization of internet usage for the WANs in app.

IMO, detect-internet just does needs to be more customizable, not removed. Most notably, the fact it will add a DHCP client automatically is where it goes afoul. It should also not default to "all" and use the WAN interface list in it's defaults when enabled.

Unless you use the mobile app, in which case it's needed and useful to show nice visualization of internet usage for the WANs in app.

这个应用程序应该娱乐eive bug reports about `internet usage` not working without detect-internet.

Unless you use the mobile app

这个应用程序应该娱乐eive bug reports about `internet usage` not working without detect-internet.

Well the app defaults to saying “not detected” so an unsuspecting user may tap it in which case it will turn it on. We handling it a branding with new default configuration that has it setup on new interface list with the explicit list of interfaces.

So it works. Just a PITA to avoid all the nasty side-effects.

I'm not sure it's related but even if "Detect internet" is disabled, we still get these strange calls to 8.8.8.8. Two adjacent ICMP echo requests every minute..