In recent releases of ROS 7, I’m getting this added to my /export output on devices with no LTE modem attached:
/interface lte apn
set [ find default=yes ] ip-type=ipv4 use-network-apn=no
If I attempt to remove it via WinBox — Interfaces → LTE tab → LTE APNs button — it complains “Couldn’t remove LTE APN - not permitted (9)”. Why? Whose router is this anyway, that I am not permitted to toss irrelevancies out from the configuration?
I fully expect that this is a no-op, but it’s annoying to have it cluttering my /export output and to have no way to remove it.
As explained in another thread, such “noise” appears when device with config based on older ROS is upgraded to newer ROS where defaults change. Upgrade always keeps (or at least tries, sometimes it fails ) current config even if it’s default. To get rid of such noise, one has to find out new defaults and set “noise ridden” configuration items to new default. Best way of getting new defaults is to have some device installed with empty config (either netinstall or reset with no config) for reference.
In particular: 7.2rc5 default properties are use-network-apn=yes ip-type=auto
Yes, “/interface/lte/apn set 0 use-network-apn=yes ip-type=auto” clears it. Thanks!
In particular, I wouldn’t have been able to construct that command without you supplying the defaults, since the symptom doesn’t occur on CHR, and I wouldn’t have been willing to reset one of my working routers to find the defaults.
Oh, I simply added new APN entry and didn’t modified default entry, so it’s ok for me.
But for anyone who edited default APN entry, reset is not happy, make sense.
) current config even if it’s default. To get rid of such noise, one has to find out new defaults and set “noise ridden” configuration items to new default. Best way of getting new defaults is to have some device installed with empty config (either netinstall or reset with no config) for reference.