And all works, but after reboot default route lte1 have more priority over l2tp-out1 default route, so internet not works until I manualy remove this route
What exactly means “interface lte1 don’t save apn profile”? I understand that without the /interface lte apn settings, add-default-route=no or default-route-distance=X cannot be applied, but why would you want to run without /interface lte apn assigned to the interface?
So it is not an intention but a bug? If so, it is worth reporting to support@mikrotik.com. But before doing that, can you define and assign the APN using winbox and then, in the Terminal window in Winbox, write /interface lte export to see whether it is saved or not?
It’s so frustrating when you ask people to do something and they waste time doing something else… I do believe you that using Winbox it behaves the way you’ve described, I just wanted to see the config export after you do it.
The problem is that most people have only one LTE modem and thus they don’t notice that whether the DHCP client is automatically added or not depends on the connection mode their particular modem supports. It seems that modems supporting “direct IP” mode (like Sierra Wireless ones) get a DHCP client attached because that interface is an “L2” one, while others supporting the “serial” interface don’t get a DHCP client assigned because that connection is a ppp over serial one and thus the address etc. are configured using ppp’s own means, not DHCP.
Which still does not explain why the apn profile disappears on restart, as it doesn’t hold only the settings controlling addition of default route (which seem to be unused if DHCP client is attached) but also the APN name.
Do I read you right that after configuration reset the APN profile does not disappear any more?
I have my first wAP LTE here. Configured it a few days ago.
Default settings…
When into LTE and APN and set up a profile for the cellular provider. APN fast.tmobile.com.
Hit apply.
I watched the log as the unit tried to register with the network… Went up and down 3 times then became steady.
Did the packages updade to current.
Reboot.
Still worked.
Updated the firmware.
Reboot
Still worked… But APN was in a different part if the interface.
Made a second APN for passing the cellular IP straight to ether 1. Selected it and got a warning about slave interface.
Connected to the wireless and removed ether1 from the bridge.
Selected the second APN.
Interface went up and down a few times… Then it showed stable.
Connected computer to ether1 and cellular IP popped up.
Never saw the APN “disappear”. Just after the software update… Editing it was moved to interface LTE.
Well, something is weird there. I’ve tried on my hAP ac (with no LTE modem actually connected but that shouldn’t matter), and regardless whether use-peer-dns and add-default-route are set to yes or no, /interface lte apn export doesn’t show the default profile at all; nevertheless, the settings do survive a reboot (/interface lte apn print does show them). When I change the apn parameter value from the default internet to something else, /interface lte apn export starts showing it. The same happens if I change default-route-distance value to something else than 2. But even in that case, the export doesn’t show the use-peer-dns and add-default-route no matter what their value is.
So I would assume that Winbox reads the configuration using an equivalent of the export and thus shows the default values of those two options which are yes. Which is definitely a bug which has remained unnoticed at least since 6.42.1 currently running on that test box till 6.42.6.
Anyone feels like testing on an 6.43rcX and then eventually sending it to support@mikrotik.com?
