Hi
I have a project where I need to ship a MikroTik LtAP mini preconfigured with SSID and password. My question is, is it possible to make one setup of the device so that it uses LTE if a SIM card is inserted or, ethernet if an ethernet connection is connected?
If so how can I do so.
Any recommendations on how to setup many devices in the fastest manner will be appreciated as well.
Martin. I am interested in exactly the same question.
It may be that the Quick Set option “Home AP” is designed to do exactly this. For what it seem to do is exclude eth1 from the default Bridge bridge and move it from the LAN to the WAN “Interface List” under Interfaces. Care is needed to define Internet Address acquisition, for which in my case it will normally be automatic with the local network defined and DHCP and NAT enabled.
This in contrast to the default Quick Set option LTE where the lte internet connection is shared across all four Ethernet ports and the WiFi.
If someone knows for sure, then please update us both?
And for bonus points, let us know what happens if both lte1 and eth1 are separate valid internet connections?
Assuming you want to prioritize ethernet, that pretty easy. In “QuickSet” section, you should be able to pick “Home AP” mode in to top-left corner. This will change the ether1 port to be a WAN port, which be used first. If there is ethernet plugged in, that be used first, then LTE be active if APN/SIM were present/configured. You can adjust the route distance field in DHCP Client and/or LTE to control the order. If there is NOT a SIM card, the LTE will not be active…so it wouldn’t be used as a route all cases.
Thanks for the response
When I change to the “Home AP” options, with the adress acquisition set to automatic, I loose internet connection and can’t get access to the router interface from browser anymore.
Perhaps I’m not sure what you’re trying to do. If the internet is on ethernet and uses DHCP, it should work. If it needs some configuration (like PPPoE, static IP, etc), then you’d still have to configure those.
The default configuration uses ether1 as a LAN port by default. So idea with “HomeAP” in QuickSet is it change that to be a WAN port. I presume you want LAN on Wi-Fi only. Otherwise, there is only 1 ethernet port, so it’s either LAN or WAN, but that take reconfiguration.
Maybe explain what you want in more detail and/or include the configuration from “:export hide-sensative” at the Terminal.
Yes I want to have internet connection to the modem over ethernet, and then wifi to my device. In my test setup I am connecting the modem to an Asus router (using ethernet). I was able to set up the modem in home AP mode yesterday, but I dit not change anything in the address acquisition section of Quick Set. I assume that means it was in Static, is it possible that it figured out the gateway IP itself? I am totally new to this kind of stuff, sorry if I am talking nonsense.
@MartinPeterson The Home AP selection takes a little longer than one expects to be implemented, so first make sure that you are sufficiently patient (unlike me first time round). 2ndly, as @Amm0 points out, your uplink needs to be connected on eth1 with the right Internet address acquisition settings & Firewall Router, DHCP & NAT checkbox selections.
With Static, I doubt that it would have been able to figure out the Gateway IP of its own accord. More likely you were just lucky with the static IP and the Netmask allowing traffic to peer between the two.
With Automatic, it most likely would have.
Anyone else reading this, how can I find out what precisely the differences are between LTE and Home AP Quicksets? Is there a script somewhere that one can view?
I’m I wrong in thinking that I should be able to put the modem in home AP mode, without any connection to the internet (No Sim and no ethernet) and be able to get to the routerOS interface by typing the 192.168.88.1 IP in a browser? When I try to do so the browser gives me an error that the adress isn’t available
Martin. It depends whether you have enable the Router/Firewall & DHCP checkboxes (and possibly also NAT) and whether the PC has a connection (wireless or/& wired using ports 2-4) with valid IP, Netmask, Gateway & DNS, normally obtained via DHCP from the Mikrotik. And that you have allowed enough time for all these to have been be applied. Although their are other valid possibilities that might work (e.g. both the Mikrotik and your browser device get compatible setting from some other available upstream current or prior DHCP server.