In testing /interface/detect-internet with r7.1rc7, I noticed it creates a DHCP client automatically. This was a surprise to me that “Detect Internet” added a persisted DHCP client, with an un-configurable “default-route-distance=1” – as such, it takes over as default route when during Internet Detect’s process. Maybe it did this V6, but our dynamic-in filter rules would caught the distance and prevent a DHCP client from setting a route at distance=1, so I wouldn’t have noticed.
Now, the DHCP client created by “Detect Internet” does have a comment with a clue what’s happening “;;; internet detect”:
/ip/dhcp-client/print
Flags: X, I, D - DYNAMIC
Columns: INTERFACE, USE-PEER-DNS, ADD-DEFAULT-ROUTE, STATUS, ADDRESS
# INTERFACE USE-PEER-DNS ADD STATUS ADDRESS
0 X vlan-internet-in no no
;;; internet detect
1 D vlan-internet-in yes yes bound 10.11.12.13
This DHCP client seems to persist, until you set internet-interface-list=“none”. The interface is a VLAN that does goes to a DMZ-type network. While that VLAN interface does have DHCP available from a different host, I didn’t expect Detect Internet to turn into Use Internet from DHCP on this particular interface.
Maybe this correct behavior. But not what’s document. The “Help” docs states for WAN (which is a prerequisite for Internet state):
Any L3 tunnel and LTE interfaces will initially have this state. Layer 2 interfaces can obtain this state if:
- an interface has an active route to 8.8.8.8 in main routing table.
- an interface can obtain (or has obtained) an address from DHCP (does not apply if DHCP server is also running Detect Internet on the DHCP server interface).
__
It doesn’t say “will obtain a DHCP address for you if needed”. The two bullets weren’t clear
if help==\[*\] then {&& or ||, (", or" | &)} else '\;-\)'
.
The config used isn’t mine – it’s what the Mikrotik iPhone smartphone (advertised at top 
) adds when some user enables it in the app:
/interface/detect-internet> export
# dec/01/2021 15:04:08 by RouterOS 7.1rc7
# model = RBD25GR-5HPacQD2HPnD
/interface detect-internet
set detect-interface-list=all internet-interface-list=WAN
So the config here isn’t my choice. And reconfiguring it in the app looked like a bad idea since it didn’t match the CLI, so didn’t try to tap the checkmark:
/interface/detect-internet> print
detect-interface-list: all
lan-interface-list: none
wan-interface-list: none
internet-interface-list: WAN
The full config is same as I posted here, which is largely my V7 test platform: http://forum.mikrotik.com/t/using-wifiwave2-to-bridge-two-audience-wirelessly-thoughts-4-address-mode/153357/1