And if they are not settable, why do they exist ? I mean why do we have in the interface many fields with “default” instead of the actual set value ?
Wouldn’t it be simpler to remove all references to default values in the Winbox and Webfig interfaces, and present the real value instead of the word “default” that seems to me really confusing ?
For example in the menu interface, loop protect, Winbox show three Loop protect states :
default
off
on
The default value is “off”. Why simply not show “off”. It seems to me that would be really less confusing for users.
It can perhaps be a little confusing, but I think it can also be useful indication of option that might have different default value in future. If you have clear preference for “on” or “off”, you can set it now and avoid being affected by future change. It’s just my guess. To make it less confusing, it could show as “default ()”.
This, unfortunate ignorance of Mikrotik.
I love the fact that someone has actually taken the time to write default = default in all value definitions in the wiki…
However, many value defaults are listed in the wiki:
yes - adjust connection MSS value
no - do not adjust connection MSS value
default - derive this value from the interface default profile; same as no if this is the interface default profile
Some values, when declared “default”, inherit its values from the interface used. So, the “default” value isn’t an arbitrary default. The real meaning is “use the already set value, to this interface, as the default for this connection”.
Guess what, we know what default means, guess what, we are just discussing the subject and would like to know when and where from they are inherited, interface is a bit vague for many settings and what the actual value presumed by default is (as a hint of what value might be the inherited one). Please don’t participate more.