MikroTik

Posted: **Fri Mar 18, 2022 6:56 pm**

New LtAP out of box does not provide IP (normally on other MikrTiks I have it gives 192.168.88.1 as it's address)
I used Winbox to get in via the MAC address and put 7.1.3 OS on it so it would detect my LTE MODEM (RM502Q)
We get internet access on the device only, it will not pass internet to the ethernet port or wireless,
The internet is there because I can check for and download updates, I can also go to terminal and run a speed test to know servers.

How do I bridge the LTE to the LAN so I can get internet on my computer or the wireless?
I have an LHG with same MODEM and that setup works fine passing internet through the ethernet port but I can't copy the LHG mipsbe config to the mmips config of the LtAP
Are there any export of interface that I can do and import them to save time?

Posted: **Sat Mar 19, 2022 8:48 am**

Are there any export of interface that I can do and import them to save time?

You cannot save a backup of the configuration and load it on another model. But you can export the configuration into a script and run that script on another device regardless its architecture. In order to make it run successfully after configuration reset, you have to modify it a bit, basically it is enough to add a :delay 1m at the beginning, provided that the number of ethernet and WiFi interfaces is the same on both the source and target device.

But from what you say, something is rotten about the LtAP, as in the default configuration, there should indeed be a 192.168.88.1/24 address attached to ether1. What does /export currently show on the LtAP?

Also, what is the /export of the LHG, i.e. do you use LTE passthrough mode or does the LHG act as a router?

Posted: **Sat Mar 19, 2022 1:49 pm**

Are there any export of interface that I can do and import them to save time?
You cannot save a backup of the configuration and load it on another model. But you can export the configuration into a script and run that script on another device regardless its architecture. In order to make it run successfully after configuration reset, you have to modify it a bit, basically it is enough to add a :delay 1m at the beginning, provided that the number of ethernet and WiFi interfaces is the same on both the source and target device.

But from what you say, something is rotten about the LtAP, as in the default configuration, there should indeed be a 192.168.88.1/24 address attached to ether1. What does /export currently show on the LtAP?

Also, what is the /export of the LHG, i.e. do you use LTE passthrough mode or does the LHG act as a router?

Here is the lTAP export, I too am concerned about not having 192.168.88.1 by default, I have tried netinstall several times.

# mar/18/2022 18:25:22 by RouterOS 7.1.3
# software id = B6QN-6MIL
#
# model = RBLtAP-2HnD
# serial number = D7250D5Exxxx
/interface bridge
add admin-mac=08:55:31:C1:xxxxx auto-mac=no comment=defconf name=bridge
/interface lte
set [ find ] allow-roaming=no band="" name=lte1 nr-band=""
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX \
disabled=no frequency=auto installation=outdoor mode=ap-bridge ssid=\
MikroTik-C18xxx
/interface list
add name=WAN
add name=LAN
/interface lte apn
set [ find default=yes ] apn=fast.t-mobile.com use-network-apn=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/port
set 0 name=serial0
set 2 name=usb3
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=wlan1
/interface list member
add interface=ether1 list=WAN
add interface=wlan1 list=LAN
/ip dhcp-client
add comment=defconf interface=bridge
/system clock
set time-zone-name=America/Chicago
/system routerboard usb
set type=mini-PCIe

Posted: **Sat Mar 19, 2022 2:29 pm**

Can you reset the LtAP to its default configuration and then export the config? There are a number of critical elements missing from your config that should be there unless you removed them or tried to import a config from another device.

Posted: **Sat Mar 19, 2022 2:35 pm**

I have tried netinstall several times.

The question is how does the default configuration look like in case of 7.1.3 on LtAP.

/system/default-configuration/print file=defconf will place the default configuration script into a file named defconf.txt, which you can download and inspect.

Other than that, what if you do /ip/address/add address=192.168.88.1/24 interface=bridge and assign some other address from 192.168.88.0/24 to your PC manually, will you be able to login via IP address rather than MAC address?

Posted: **Sat Mar 19, 2022 3:47 pm**

@sindy, I think this thread is a continuation of viewtopic.php?t=182960 ...

The default configuration is really just those lines on the LtAP, it starts as the "WISP AP" default it seems

But I can see the confusion here. Looking at the QuickSet profiles, none support LTE. While most LTE RBs have either "LTE AP" or "LTE" as a QuickSet profiles. BUT despite the LtAP having SIM slots, it does not have any LTE-based QuickSet profiles...

You could try the "Home AP" mode, that will get you a Wi-Fi network with a LAN to test the LTE part. But you'd have change ether1 by removing the /ip/dhcp-client on ether1, and adding ether1 to the /interface/bridge/port

I grabbed the 7.1.3 output of the /system/default-config from an LtAP at 7.1.3 here:

# sep/ 2/2020  3: 9:38 by RouterOS 7.1.3
# software id = ZFR6-6BCM
#
            script: #| Welcome to RouterOS!
                    #|    1) Set a strong router password in the System > Users menu
                    #|    2) Upgrade the software in the System > Packages menu
                    #|    3) Enable firewall on untrusted networks
                    #|    4) Set your country name to observe wireless regulations
                    #| -----------------------------------------------------------------------------
                    #| WISP Bridge:
                    #|  * wireless and LAN interfaces are bridged;
                    #| wlan1 Configuration:
                    #|     mode:                ap-bridge;
                    #|     band:                2ghz-b/g/n;
                    #|     tx-chains:           0;1;
                    #|     rx-chains:           0;1;
                    #|     installation:        outdoor;
                    #|     wpa2:      no;
                    #|     ht-extension:        20/40mhz-XX;
                    #| LAN Configuration:
                    #|     DHCP Client: enabled on bridge (LAN port);
                    
                    :global ssid;
                    :global defconfMode;
                    :log info "Starting defconf script";
                    #-------------------------------------------------------------------------------
                    # Apply configuration.
                    # these commands are executed after installation or configuration reset
                    #-------------------------------------------------------------------------------
                    :if ($action = "apply") do={
                      # wait for interfaces
                      :local count 0;
                      :while ([/interface ethernet find] = "") do={
                        :if ($count = 30) do={
                          :log warning "DefConf: Unable to find ethernet interfaces";
                          /quit;
                        }
                        :delay 1s; :set count ($count +1); 
                      };
                      :local count 0;
                      :while ([/interface wireless print count-only] < 1) do={ 
                        :set count ($count +1);
                        :if ($count = 40) do={
                          :log warning "DefConf: Unable to find wireless interface(s)"; 
                          /ip address add address=192.168.88.1/24 interface=ether1 comment="defconf";
                          /quit
                        }
                        :delay 1s;
                      };
                      /interface wireless {
                    :local ifcId [/interface wireless find where default-name=wlan1]
                    :local currentName [/interface wireless get $ifcId name]
                        set $ifcId mode=ap-bridge band=2ghz-b/g/n disabled=no wireless-protocol=any \
                           distance=dynamic installation=outdoor
                        set $ifcId channel-width=20/40mhz-XX;
                        set $ifcId frequency=auto
                        :local wlanMac  [/interface wireless get $ifcId mac-address];
                        :set ssid "MikroTik-$[:pick $wlanMac 9 11]$[:pick $wlanMac 12 14]$[:pick $wlanMac 15 17]"
                        set $ifcId ssid=$ssid
                      }
                     /interface bridge
                       add name=bridge disabled=no auto-mac=yes protocol-mode=rstp comment=defconf;
                     :local bMACIsSet 0;
                     :foreach k in=[/interface find where !(slave=yes   || name~"bridge")] do={
                       :local tmpPortName [/interface get $k name];
                       :if ($bMACIsSet = 0) do={
                         :if ([/interface get $k type] = "ether") do={
                           /interface bridge set "bridge" auto-mac=no admin-mac=[/interface get $tmpPortName mac-address];
                           :set bMACIsSet 1;
                         }
                       }
                         :if (([/interface get $k type] != "ppp-out") && ([/interface get $k type] != "lte")) do={
                           /interface bridge port
                             add bridge=bridge interface=$tmpPortName comment=defconf;
                         }
                       }
                      /ip dhcp-client add interface=bridge disabled=no comment="defconf";
                    }
                    #-------------------------------------------------------------------------------
                    # Revert configuration.
                    # these commands are executed if user requests to remove default configuration
                    #-------------------------------------------------------------------------------
                    :if ($action = "revert") do={
                    /user set admin password=""
                     /system routerboard mode-button set enabled=no
                     /system routerboard mode-button set on-event=""
                     /system script remove [find comment~"defconf"]
                     /ip firewall filter remove [find comment~"defconf"]
                     /ipv6 firewall filter remove [find comment~"defconf"]
                     /ipv6 firewall address-list remove [find comment~"defconf"]
                     /ip firewall nat remove [find comment~"defconf"]
                     /interface list member remove [find comment~"defconf"]
                     /interface detect-internet set detect-interface-list=none
                     /interface detect-internet set lan-interface-list=none
                     /interface detect-internet set wan-interface-list=none
                     /interface detect-internet set internet-interface-list=none
                     /interface list remove [find comment~"defconf"]
                     /tool mac-server set allowed-interface-list=all
                     /tool mac-server mac-winbox set allowed-interface-list=all
                     /ip neighbor discovery-settings set discover-interface-list=!dynamic
                       :local o [/ip dhcp-server network find comment="defconf"]
                       :if ([:len $o] != 0) do={ /ip dhcp-server network remove $o }
                       :local o [/ip dhcp-server find name="defconf" !disabled]
                       :if ([:len $o] != 0) do={ /ip dhcp-server remove $o }
                       /ip pool {
                         :local o [find name="default-dhcp" ranges=192.168.88.10-192.168.88.254]
                         :if ([:len $o] != 0) do={ remove $o }
                       }
                       :local o [/ip dhcp-client find comment="defconf"]
                       :if ([:len $o] != 0) do={ /ip dhcp-client remove $o }
                     /ip dns {
                       set allow-remote-requests=no
                       :local o [static find comment="defconf"]
                       :if ([:len $o] != 0) do={ static remove $o }
                     }
                     /ip address {
                       :local o [find comment="defconf"]
                       :if ([:len $o] != 0) do={ remove $o }
                     }
                     :foreach iface in=[/interface ethernet find] do={
                       /interface ethernet set $iface name=[get $iface default-name]
                     }
                     /interface bridge port remove [find comment="defconf"]
                     /interface bridge remove [find comment="defconf"]
                     /interface bonding remove [find comment="defconf"]
                     /interface wireless cap set enabled=no interfaces="" caps-man-addresses=""
                     /interface wireless reset-configuration wlan1
                     /interface wireless security-profile set default mode=none\
                          authentication-types="" disable-pmkid=no wpa2-pre-shared-key="" comment="" 
                      /caps-man manager set enabled=no
                      /caps-man manager interface remove [find comment="defconf"]
                      /caps-man manager interface set [ find default=yes ] forbid=no
                      /caps-man provisioning remove [find comment="defconf"]
                      /caps-man configuration remove [find comment="defconf"]
                    }
                    :log info Defconf_script_finished;
                    :set defconfMode;
                    :set ssid;
                    
  caps-mode-script: #-------------------------------------------------------------------------------
                    # Note: script will not execute at all (will throw a syntax error) if
                    #       dhcp or wireless-fp packages are not installed
                    #-------------------------------------------------------------------------------
                    
                    #| CAP configuration
                    #|
                    #|   Wireless interfaces are set to be managed by CAPsMAN.
                    #|   All ethernet interfaces and CAPsMAN managed interfaces are bridged.
                    #|   DHCP client is set on bridge interface.
                    
                    # bridge port name
                    :global brName  "bridgeLocal";
                    :global logPref "defconf:";
                    
                    
                    :global action;
                    
                    :log info $action
                    
                    :if ($action = "apply") do={
                    
                      # wait for ethernet interfaces
                      :local count 0;
                      :while ([/interface ethernet find] = "") do={
                        :if ($count = 30) do={
                          :log warning "DefConf: Unable to find ethernet interfaces";
                          /quit;
                        }
                        :delay 1s; :set count ($count + 1);
                      }
                    
                      :local macSet 0;
                      :local tmpMac "";
                    
                      :foreach k in=[/interface ethernet find] do={
                        # first ethernet is found; add bridge and set mac address of the ethernet port
                        :if ($macSet = 0) do={
                          :set tmpMac [/interface ethernet get $k mac-address];
                          /interface bridge add name=$brName auto-mac=no admin-mac=$tmpMac comment="defconf";
                          :set macSet 1;
                        }
                        # add bridge ports
                        /interface bridge port add bridge=$brName interface=$k comment="defconf"
                      }
                    
                      # try to add dhcp client on bridge interface (may fail if already exist)
                      :do {
                        /ip dhcp-client add interface=$brName disabled=no comment="defconf"
                      } on-error={ :log warning "$logPref unable to add dhcp client";}
                    
                    
                      # try to configure caps (may fail if for example specified interfaces are missing)
                      :local interfacesList "";
                      :local bFirst 1;
                    
                      # wait for wireless interfaces
                      :while ([/interface wireless find] = "") do={
                        :if ($count = 30) do={
                          :log warning "DefConf: Unable to find wireless interfaces";
                          /quit;
                        }
                        :delay 1s; :set count ($count + 1);
                      }
                    
                      # delay just to make sure that all wireless interfaces are loaded
                      :delay 5s;
                      :foreach i in=[/interface wireless find] do={
                        if ($bFirst = 1) do={
                          :set interfacesList [/interface wireless get $i name];
                          :set bFirst 0;
                        } else={
                          :set interfacesList "$interfacesList,$[/interface wireless get $i name]";
                        }
                      }
                      :do {
                        /interface wireless cap
                          set enabled=yes interfaces=$interfacesList discovery-interfaces=$brName bridge=$brName
                      } on-error={ :log warning "$logPref unable to configure caps";}
                    
                    }
                    
                    :if ($action = "revert") do={
                      :do {
                        /interface wireless cap
                          set enabled=no interfaces="" discovery-interfaces="" bridge=none
                      } on-error={ :log warning "$logPref unable to unset caps";}
                    
                      :local o [/ip dhcp-client find comment="defconf"]
                      :if ([:len $o] != 0) do={ /ip dhcp-client remove $o }
                    
                      /interface bridge port remove [find comment="defconf"]
                      /interface bridge remove [find comment="defconf"]
                    
                    }
     custom-script:

Posted: **Sat Mar 19, 2022 4:13 pm**

To clarify how to use the "Home AP" QuickSet profile to get you a LAN (e.g. "a 192.168.88.1 address"), and have ether1 be a LAN port, you'd fill in QuickSet something like this:

After that, ether1 is a "WAN" port, which is likely not what you want. To change the port to a LAN port (e.g. it give out a 192.168.88.x address), you'd just need to disable the DHCP client, add the port the bridge, and remove ether1 from the WAN list.

/ip/dhcp-client/disable [find interface~"bridge"]
/interface/bridge/port/enable [find interface=ether1]
/interface/list/member/remove [/interface/list/member/find list=WAN interface=ether1]

Your next task would be making sure LTE works, by pinging from router terminal etc. Assuming LTE was connect/had IP address, the last thing be the "lte1" (or "lte2", or potentially "ppp-out1"...) interface are in the WAN interface list (your LTE interface names may be different, but typically):
/interface/list/member/add list=WAN interface=lte1
/interface/list/member/add list=WAN interface=lte2

Posted: **Sat Mar 19, 2022 6:53 pm**

I have tried netinstall several times.
The question is how does the default configuration look like in case of 7.1.3 on LtAP.

/system/default-configuration/print file=defconf will place the default configuration script into a file named defconf.txt, which you can download and inspect.

Other than that, what if you do /ip/address/add address=192.168.88.1/24 interface=bridge and assign some other address from 192.168.88.0/24 to your PC manually, will you be able to login via IP address rather than MAC address?

Unfortunately, what I copied and pasted is all that is there after a rest and after netinstall... it's weird. I built it up and manually added IP and DHCP values etc. Got internet working and did a full back up. Decided to do a fresh netinstall and restore the backup but again no IP or access unless I used winbox mac address. LTE not in the drop down list. Eventually after adding it all back manually the QuickSet now shows LTE options. I just wanted to see if this is normal LtAP behavior or if mine is goofy right out of the box.

Posted: **Sat Mar 19, 2022 7:01 pm**

@sindy, I think this thread is a continuation of viewtopic.php?t=182960 ...

The default configuration is really just those lines on the LtAP, it starts as the "WISP AP" default it seems

But I can see the confusion here. Looking at the QuickSet profiles, none support LTE. While most LTE RBs have either "LTE AP" or "LTE" as a QuickSet profiles. BUT despite the LtAP having SIM slots, it does not have any LTE-based QuickSet profiles...

You could try the "Home AP" mode, that will get you a Wi-Fi network with a LAN to test the LTE part. But you'd have change ether1 by removing the /ip/dhcp-client on ether1, and adding ether1 to the /interface/bridge/port

I grabbed the 7.1.3 output of the /system/default-config from an LtAP at 7.1.3 here:

Can I just add the script you posted to mine?
Each time I upgrade firmware or reset this unit I'm stuck with no 192.168.88.1 and that weirds me out.
I saw your follow up reply to help me configure it further but as I finally got a working system now and backed it up.... my confidence in the device is still none because I did a fresh netinstall and restored the backup only to have dhcp, lte and main IP all absent.

Posted: **Sat Mar 19, 2022 7:07 pm**

I just wanted to see if this is normal LtAP behavior or if mine is goofy right out of the box.

That's why I've suggested you to dump the default configuration script and see whether it adds the IP address etc. Since you can add all that manually, the hardware is not broken. Hence the most likely thing is a suboptimal contents of the default configuration script in the 7.1.3 package for the mmips architecture.

Posted: **Sat Mar 19, 2022 7:13 pm**

I just wanted to see if this is normal LtAP behavior or if mine is goofy right out of the box.
That's why I've suggested you to dump the default configuration script and see whether it adds the IP address etc. Since you can add all that manually, the hardware is not broken. Hence the most likely thing is a suboptimal contents of the default configuration script in the 7.1.3 package for the mmips architecture.

Where can I get a good known working copy of 7.1.3 then? I obtained mine from MikrTik's website.

Posted: **Sat Mar 19, 2022 7:17 pm**

Where can I get a good known working copy of 7.1.3 then? I obtained mine from MikrTik's website.

I don't say it broke during download. If it indeed doesn't set the items you're missing, it has been broken in development.

Posted: **Sat Mar 19, 2022 7:24 pm**

I just wanted to see if this is normal LtAP behavior or if mine is goofy right out of the box.
That's why I've suggested you to dump the default configuration script and see whether it adds the IP address etc. Since you can add all that manually, the hardware is not broken. Hence the most likely thing is a suboptimal contents of the default configuration script in the 7.1.3 package for the mmips architecture.

It more the default config is different than the LHRG etc, thus why the OP is having issues since the default isn't just working.... The LtAP default uses a bridge with a DHCP client, both ether1 and wlan1 are part of the bridge, with no /ip/address (e.g. default is DHCP from ether1). That seem the V7 defaults in both 7.1.3 and rc7.2rc4.

While the LHRG uses the "LTE" default, which is a LAN on ether1.

So what @sindy is trying to say is you need to add your LAN, which starts with IP. Either by manual adding an IP addresss, DHCP server, etc., or using QuickSet with the added config after I suggest. Re-running netinstall isn't going to help, the default is getting applied as-designed (but not desired, for your application).

Posted: **Sat Mar 19, 2022 7:42 pm**

I would suggest you to reset to defaults, then upgrade to 7.1.3 and test again...

Posted: **Sat Mar 19, 2022 7:47 pm**

I would suggest you to reset to defaults, then upgrade to 7.1.3 and test again...

Look into the default configuration script of 7.1.3 as posted by @Amm0 in this post. It sets exactly what OP is getting. No point in spawning it over and over again, the result will be the same.

It is a question for Mikrotik devs why they did it this way for LtAP. Normally, the dhcp client attachment to a bridge is a CAP default configuration, while the standard default configuration is 192.168.88.1/24 and dhcp server attached to the bridge.

Posted: **Sat Mar 19, 2022 7:47 pm**

Mikrotik help page on "Default Configuration" has a clue on what's going on here. See https://help.mikrotik.com/docs/display/ ... igurations

If the LtAP comes without any Mikrotik LTE modems install, comes to the "WISP Bridge" configuration. While LtAP that come with Mikrotik LTE modems (e.g. "4G kit", etc), default to "LTE CPE AP Router".

But all the LtAP should still at least have the same potential alternative defaults in QuickSet IMO. But regardless, if you apply the "Home AP" configuration from the screensoot, then paste in the 5 config lines, it should works the same as the "LTE CPE AP Router" config "flavor" that be on LHGG/SXT/wAP/etc.

Obviously if you reset to defaults or do netinstall, any QuickSet or other configuration will be lost & you'll be back the "WISP Bridge" mode.

Posted: **Sat Mar 19, 2022 7:53 pm**

Mikrotik help page on "Default Configuration" has a clue on what's going on here. See https://help.mikrotik.com/docs/display/ ... igurations

If the LtAP comes without any Mikrotik LTE modems install, comes to the "WISP Bridge" configuration. While LtAP that come with Mikrotik LTE modems (e.g. "4G kit", etc), default to "LTE CPE AP Router".

But all the LtAP should still at least have the same potential alternative defaults in QuickSet IMO. But regardless, if you apply the "Home AP" configuration from the screensoot, then paste in the 5 config lines, it should works the same as the "LTE CPE AP Router" config "flavor" that be on LHGG/SXT/wAP/etc.

Obviously if you reset to defaults or do netinstall, any QuickSet or other configuration will be lost & you'll be back the "WISP Bridge" mode.

How can I grab the 7.1.3 output of the /system/default-config from my LtAP?

All I see is:

/interface bridge
add admin-mac=08:55:31:C1:xxxxx auto-mac=no comment=defconf name=bridge
/interface lte
set [ find ] allow-roaming=yes band="" name=lte1 nr-band=""
/interface wireless
set [ find default-name=wlan1 ] adaptive-noise-immunity=ap-and-client-mode \
ampdu-priorities=0,1,2,3 antenna-mode=rxa-txb band=2ghz-onlyn country=\
"united states3" disabled=no distance=indoors frame-lifetime=1 frequency=\
auto mode=ap-bridge ssid=MikroTik wireless-protocol=802.11 wmm-support=\
enabled
/interface list
add name=WAN
add name=LAN
/interface lte apn
set [ find default=yes ] apn=fast.t-mobile.com
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.2.20-192.168.2.200
/ip dhcp-server
add address-pool=dhcp interface=bridge name=dhcp1
/port
set 0 name=serial0
set 2 name=usb3
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface detect-internet
set detect-interface-list=all
/interface list member
add interface=wlan1 list=LAN
add interface=lte1 list=WAN
add interface=bridge list=LAN
/interface wireless cap
set bridge=bridge interfaces=wlan1
/ip address
add address=192.168.2.1/24 interface=bridge network=192.168.2.0
/ip dhcp-client
add
/ip dhcp-server network
add address=0.0.0.0/24 gateway=0.0.0.0 netmask=24
add address=192.168.2.0/24 gateway=192.168.2.1 netmask=24
/ip firewall filter
add action=accept chain=input protocol=icmp
add action=accept chain=input comment="Allow Remote Winbox" in-interface=\
RemoteWinboxVPN-BITHAULERS
add action=accept chain=input connection-state=established
add action=accept chain=input connection-state=related
add action=drop chain=input in-interface-list=!LAN
/ip firewall mangle
add action=change-ttl chain=postrouting new-ttl=set:65 passthrough=yes
/ip firewall nat
add action=masquerade chain=srcnat out-interface-list=WAN
add action=masquerade chain=srcnat out-interface-list=WAN
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=bridge type=internal
add interface=lte1 type=external
/system clock
set time-zone-name=America/Chicago
/system package update
set channel=testing
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

Posted: **Sat Mar 19, 2022 7:55 pm**

I would suggest you to reset to defaults, then upgrade to 7.1.3 and test again...
Look into the default configuration script of 7.1.3 as posted by @Amm0 in this post. It sets exactly what OP is getting. No point in spawning it over and over again, the result will be the same.

@sindy i installed a LTAP LTE6 this week.
I noticed nothing strange compared to other MikroTIK LTE devices i' ve used ( WAP, WAP LTE6, LHGG,) as far as the configuration is concerned .

Also since the OP does not need any complex configuration, i would suggest not using quickset.
Just let the defaults and if you need any changes do them manually.

Also i see detect-internet enabled, why?
Also the config shows some duplicates , maybe because of running quickset multiple times ? I don't know, i never use it, but does not look normal..
All those suggest a reset and fresh start for me...

Posted: **Sat Mar 19, 2022 7:56 pm**

How can I grab the 7.1.3 output of the /system/default-config from my LtAP?

The way I've suggested above. But you don't need to do that - @Amm0 has already posted the result a few posts earlier.

Simply put: your LtAP behaves exactly as intended and documented by Mikrotik, it ain't broken.

Posted: **Sat Mar 19, 2022 7:59 pm**

@sindy i installed a LTAP LTE6 this week.
I noticed nothing strange compared to other MikroTIK LTE devices i' ve used ( WAP, WAP LTE6, LHGG,) as far as the configuration is concerned .

As @Amm0 wrote above, there is a difference between the default configuration script of an LtAP "LTE(6) kit" (where the LTE modem is pre-installed by Mikrotik) and the default configuration script of a bare LtAP shipped without any LTE modem.

Posted: **Sat Mar 19, 2022 8:00 pm**

Yup we got the defaults. FWIW, I opened a ticket with Mikrotik since it seem a poor choice of defaults.

So if your config is working, great.

But you might want to remove any IP>DHCP Client and in IP>DHCP Server>Network remove the 0.0.0.0/24 network. Both should be harmless, both are an unfortunate side-effect of QuickSet.

Posted: **Sat Mar 19, 2022 8:01 pm**

Mikrotik help page on "Default Configuration" has a clue on what's going on here. See https://help.mikrotik.com/docs/display/ ... igurations

If the LtAP comes without any Mikrotik LTE modems install, comes to the "WISP Bridge" configuration. While LtAP that come with Mikrotik LTE modems (e.g. "4G kit", etc), default to "LTE CPE AP Router".

But all the LtAP should still at least have the same potential alternative defaults in QuickSet IMO. But regardless, if you apply the "Home AP" configuration from the screensoot, then paste in the 5 config lines, it should works the same as the "LTE CPE AP Router" config "flavor" that be on LHGG/SXT/wAP/etc.

Obviously if you reset to defaults or do netinstall, any QuickSet or other configuration will be lost & you'll be back the "WISP Bridge" mode.

Actually now I'm wondeing where can I get the default configurations from? I could just load them if I had them, right?

Posted: **Sat Mar 19, 2022 8:04 pm**

@sindy i installed a LTAP LTE6 this week.
I noticed nothing strange compared to other MikroTIK LTE devices i' ve used ( WAP, WAP LTE6, LHGG,) as far as the configuration is concerned .
As @Amm0 wrote above, there is a difference between the default configuration script of an LtAP "LTE(6) kit" (where the LTE modem is pre-installed by Mikrotik) and the default configuration script of a bare LtAP shipped without any LTE modem.

ok @sindy, i see your point... My first step always when logging in to a new device is reset to no defaults, so i don't really look what the defaults are or not...
Then a reset to no-defaults and step by step configuration with no quickset...

Posted: **Sat Mar 19, 2022 8:10 pm**

Re default from another LtAP WITH modems, not sure that be helpful. It's not going to fix how QuickSet works & you'd really end up at the same place you are now. I would remove the extraneous lines as suggested.

The only reason I suggested QuickSet was that it would proximate what the defaults from a LtAP with modem would do. The "Home AP" and "LTE CPE AP" are nearly identical on other units, one just deals with the APN and shows signal in QuickSet. But you wouldn't get that by just applying the default configuration from another LtAP on top of this one.

Posted: **Sat Mar 19, 2022 8:19 pm**

ok @sindy, i see your point... My first step always when logging in to a new device is reset to no defaults, so i don't really look what the defaults are or not...
Then a reset to no-defaults and step by step configuration with no quickset...

I think the OP has an SXT and/or LHGG, and guessing the defaults "just worked" out-of-the-box of those. While he set the APN, t-mobile doesn't care so good chance those unit work if you just put in a SIM card. No config required

.

Just a guess here, be curious to confirm if that was @cascom experience?

Posted: **Sat Mar 19, 2022 8:36 pm**

ok @sindy, i see your point... My first step always when logging in to a new device is reset to no defaults, so i don't really look what the defaults are or not...
Then a reset to no-defaults and step by step configuration with no quickset...
I think the OP has an SXT and/or LHGG, and guessing the defaults "just worked" out-of-the-box of those. While he set the APN, t-mobile doesn't care so good chance those unit work if you just put in a SIM card. No config required .

Just a guess here, be curious to confirm if that was @cascom experience?

Kind of, with the sxt and LHG all I did was change the APN after allowing the default suggested config to be applied.
When firing up the LtAP I also chose yes to apply the default config.... the initial difference is the LtAP did not provide an IP at all ever.... Winbox only showed MAC Address and blank IP no matter how many resets, updates, netinstalls and restores. The SXT and LHG always gave me 192.168.88.1

Now all of a sudden my LtAP has the LTE options in quickset but does not offer any values in the fields... I have to enter 192.168.xxx.xxx myself.
As long as the device is not broken I'm relieved... will struggle to grasp the LAN and WAN and BRIDGE stuff Lol. But I'm sure it will click.
After a reboot it takes my wireless devices about 3 min to get internet - good. However, my hardwired PC to the LAN port takes about 6 minutes.
I will clean up the lines you suggested and re-eval it.

Do you think an LtAP with a MODEM from factory will behave different after netinstalls done to it as well or am I off there? Are we still saying the file from MikroTik is just missing a few basics?

Posted: **Sat Mar 19, 2022 8:45 pm**

Here https://help.mikrotik.com/docs/display/ ... tupexample you can see the APN configuration...
Then, in a simple Router setup, create a Bridge and add the ether1 and wlan interfaces as ports, set an IP address to the Bridge interface e.g. 192.168.1.1/24, create a DHCP server on the Bridge interface, set a DNS server and allow remote requests and masquerade your LTE interface...
The above configuration should give you access to the internet from a Client PC...
Ofcorse you need to setup your Firewall...
https://help.mikrotik.com/docs/display/ ... t+Firewall

My suggestion would be to reset to no defaults and try configure step by step your device...

Posted: **Sat Mar 19, 2022 8:52 pm**

Here https://help.mikrotik.com/docs/display/ ... tupexample you can see the APN configuration...
Then, in a simple Router setup, create a Bridge and add the ether1 and wlan interfaces as ports, set an IP address to the Bridge interface e.g. 192.168.1.1/24, create a DHCP server on the Bridge interface, set a DNS server and allow remote requests and masquerade your LTE interface...
The above configuration should give you access to the internet from a Client PC...
Ofcorse you need to setup your Firewall...
https://help.mikrotik.com/docs/display/ ... t+Firewall

My suggestion would be to reset to no defaults and try configure step by step your device...

Everyone has been so helpful and the config tips get me going however, defaulting and resetting and netinstalls all get me back to my same problem... the device only offers a MAC address in Winbox, it won't ever get to 192.168.88.1 as all other MikroTik devices I have worked with. Should I be concerned about that?

Posted: **Sat Mar 19, 2022 9:00 pm**

Here https://help.mikrotik.com/docs/display/ ... tupexample you can see the APN configuration...
Then, in a simple Router setup, create a Bridge and add the ether1 and wlan interfaces as ports, set an IP address to the Bridge interface e.g. 192.168.1.1/24, create a DHCP server on the Bridge interface, set a DNS server and allow remote requests and masquerade your LTE interface...
The above configuration should give you access to the internet from a Client PC...
Ofcorse you need to setup your Firewall...
https://help.mikrotik.com/docs/display/ ... t+Firewall

My suggestion would be to reset to no defaults and try configure step by step your device...
Everyone has been so helpful and the config tips get me going however, defaulting and resetting and netinstalls all get me back to my same problem... the device only offers a MAC address in Winbox, it won't ever get to 192.168.88.1 as all other MikroTik devices I have worked with. Should I be concerned about that?

No.

Do you think an LtAP with a MODEM from factory will behave different after netinstalls done to it as well or am I off there?

I think it must know from some hardware id someplace it's the "LtAP without modems". This is MAYBE what's guiding what ROS is using for defaults. So not sure how to trick it get different defaults.

Are we still saying the file from MikroTik is just missing a few basics?

Well, the LtAP is not quite a home device nor an enterprise device, it is middle... And you have one that, by default, has no modems. So Mikrotik has to pick something as a default to ship on it. Now they assume the more common case for a device with 3 SIM slots is as a 2.4Ghz Wi-Fi repeater, even though it has only pretty underpowered internal antennas for Wi-Fi. That's a questionable call IMO, but argueable not a "bug"

The 2nd problem is QuickSet, both specifically here and generally speaking

. You should have been able to pick an "alternative default" using one of the QuickSet profile in the upper left. But what should be an easy-to-use config tool, it often cause way more problems than it solves. e.g. the 0.0.0.0 DHCP network that shouldn't be there.

But if this is working, create a "/file/backup" and "/export show-sensative" to save it off for youself. You can always use the backup file to get "YOUR default" back and forget about whatever default the LtAP comes with OR QuickSet. You seemingly have a "base" config for your needs.

Posted: **Sat Mar 19, 2022 9:08 pm**

Everyone has been so helpful and the config tips get me going however, defaulting and resetting and netinstalls all get me back to my same problem...

Can you please /export hide-sensitive the configuration you have after reset to no defaults was made ?

Posted: **Sat Mar 19, 2022 9:16 pm**

Everyone has been so helpful and the config tips get me going however, defaulting and resetting and netinstalls all get me back to my same problem...
Can you please /export hide-sensitive the configuration you have after reset to no defaults was made ?

# mar/18/2022 18:25:22 by RouterOS 7.1.3
# software id = B6QN-6MIL
#
# model = RBLtAP-2HnD
# serial number = D7250D5Exxxx
/interface bridge
add admin-mac=08:55:31:C1:xxxxx auto-mac=no comment=defconf name=bridge
/interface lte
set [ find ] allow-roaming=no band="" name=lte1 nr-band=""
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX \
disabled=no frequency=auto installation=outdoor mode=ap-bridge ssid=\
MikroTik-C18xxx
/interface list
add name=WAN
add name=LAN
/interface lte apn
set [ find default=yes ] apn=fast.t-mobile.com use-network-apn=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/port
set 0 name=serial0
set 2 name=usb3
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=wlan1
/interface list member
add interface=ether1 list=WAN
add interface=wlan1 list=LAN
/ip dhcp-client
add comment=defconf interface=bridge
/system clock
set time-zone-name=America/Chicago
/system routerboard usb
set type=mini-PCIe

Posted: **Sun Mar 20, 2022 6:43 pm**

ether1 is not your WAN port... lte1 is your WAN port...
So remove ether1 from the WAN list and add your lte interface...

Also i see no masquerade rule for your LTE interface...

ip firewall/nat/add chain=srcnat out-interface-list=WAN action=masquerade

No IP address assignment on your Bridge and no DHCP servers...
e.g.

ip address/add address=192.168.1.1/24 interface=Bridge

Posted: **Sun Mar 20, 2022 6:43 pm**

Your LHGG has a default configuration that just works with LTE and creates LAN on ether1. The issue here is NO default configuration is going to do that on the LtAP version you have. So basically you're going to have tackle on the LtAP, one way or another.

Can you please /export hide-sensitive the configuration you have after reset to no defaults was made ?

@cascom, that actually just the default configuration, NOT the no-default=yes version. @Zacharias was suggesting using:

/system reset-configuration no-defaults=yes keep-users=yes

Basically you need to configure your router ONCE, and then NEVER use reset-configuration, netinstall, etc again.

The only issue here is you may not be familar with what it takes to setup a router from scratch. This is what @Zacharias suggests. This approach is worth-while since you'd actually understand all the lines in the configuration. Mikrotik's newer doc on "First Time Step" do cover all the steps pretty well: https://help.mikrotik.com/docs/display/ ... figuration

They don't cover LTE there, but that part is covered here, so you can skip the section about "Configuring Internet Connection" in the first guide, since this covers the LTE part: https://help.mikrotik.com/docs/display/ ... tupexample

Or, you can go back to the QuickSet + "5 lines" I shared above, see posting.php?mode=quote&p=920182#pr920144 and if you have an problem, post the config with the problem you're having. I think you're only having trouble since the LtAP comes with a poor set of defaults but since you do have configure it somewhat from defaults it kinda doesn't matter what it starts with.

I do think it might be a useful exercise to go through "from scratch" as @Zacharias and @sindy suggested here. That means largely starting at step one at Mikrotik "First Time Setup" guide. At then end, you'd have a pretty good confidence in your configuration. Otherwise, apply the "Home AP" and move the port in the bridge, that will get you a decent firewall and LAN in the minimum number of steps - but yeah if you can't read the config, hard to have confidence on a Mikrotik

Posted: **Mon Mar 21, 2022 4:10 am**

ether1 is not your WAN port... lte1 is your WAN port...
So remove ether1 from the WAN list and add your lte interface...

Also i see no masquerade rule for your LTE interface...
Code: Select all
ip firewall/nat/add chain=srcnat out-interface-list=WAN action=masquerade
No IP address assignment on your Bridge and no DHCP servers...
e.g.
Code: Select all
ip address/add address=192.168.1.1/24 interface=Bridge 

Thank you for that, also @ammo and the rest have been great... ended up making an RMA as more issue continued. Random reboots, wifi drops and general loss of connection thru winbox after sitting for a while. I will post updates when I get the nnew LtAP, maybe I'll ge tit with a MODEM pre-installed.

Posted: **Mon Apr 11, 2022 5:29 pm**

Your LHGG has a default configuration that just works with LTE and creates LAN on ether1. The issue here is NO default configuration is going to do that on the LtAP version you have. So basically you're going to have tackle on the LtAP, one way or another.

I have now done this on 3 different brand new LtAP units and all behave same or worse.
The main symptoms I have narrowed down are none of them will stay accessible via the ethernet port, this issue is by far the worst. I can get service up and running on the internet but after a reboot I sometimes lose the ability to communicate via winbox unless I go wifi. When I ethernet I regularly lose internet connection but again on wifi it's fine.
In some random cases the the device loses the LTE quickset options from the drop down menu.
If I leave it alone and don;t use the Ethernet port then the system is stable, I just can't rely on it... I don't want to deploy for wifi applications only (I need the eth1 to work fully)

Posted: **Mon Apr 11, 2022 5:51 pm**

Your LHGG has a default configuration that just works with LTE and creates LAN on ether1. The issue here is NO default configuration is going to do that on the LtAP version you have. So basically you're going to have tackle on the LtAP, one way or another.

I have now done this on 3 different brand new LtAP units and all behave same or worse.
The main symptoms I have narrowed down are none of them will stay accessible via the ethernet port, this issue is by far the worst. I can get service up and running on the internet but after a reboot I sometimes lose the ability to communicate via winbox unless I go wifi. When I ethernet I regularly lose internet connection but again on wifi it's fine.
In some random cases the the device loses the LTE quickset options from the drop down menu.
If I leave it alone and don;t use the Ethernet port then the system is stable, I just can't rely on it... I don't want to deploy for wifi applications only (I need the eth1 to work fully)

What are you seeing in the logs? If it's a crash, that explain "losing a port". M/R/STP could also explain ports going "dead"...are the LtAP plugged into a larger network switch (e.g. a cisco etc with bpdu-guard enable)?

In terms of QuickSet, that part is tricky. It doesn't "store the mode" you are using. Instead, QuickSet "detects" the mode based on interface names and comments. As a result, if the LTE modem is what's having an issue, say the LTE interface isn't up – QuickSet would think that's a non-LTE config in use. Let's table this part for now.

Can you one of the configs you're using currently? And check the logs to see if you see error or reboots, crashes, and/or if the LTE interface is having any issues (e.g. before getting to the ethernet port).

Posted: **Mon Apr 11, 2022 5:54 pm**

I'd also recommend trying 7.2. It has a lot of LTE fixes over any of the 7.1.x versions.

Posted: **Tue Apr 12, 2022 1:12 am**

I'd also recommend trying 7.2. It has a lot of LTE fixes over any of the 7.1.x versions.

I am on 7.2 both OS and firmware

What are you seeing in the logs? If it's a crash, that explain "losing a port". M/R/STP could also explain ports going "dead"...are the LtAP plugged into a larger network switch (e.g. a cisco etc with bpdu-guard enable)?
No crash, just a deassigned meassge in log file. It does lose LTE occasionally.
If I keep rebooting then eventually it stays working... very odd.
Today, it showed internet, but connected PC nor updates from winbox would talk to internet
Rebooted and used wifi to connect to router and internet was fine on both
Rebooted with lan attached and no internet on PC but upate server okay from winbox and wifi to phone good also... maybe its an ipv6 problem conflict?
As soon as I turn PC wifi on and connect then it works too.

In terms of QuickSet, that part is tricky. It doesn't "store the mode" you are using. Instead, QuickSet "detects" the mode based on interface names and comments. As a result, if the LTE modem is what's having an issue, say the LTE interface isn't up – QuickSet would think that's a non-LTE config in use. Let's table this part for now.
How can I build the unit after a rest?
All I want is LTE to be the internet source, and the output to be the Ethernet port.

Can you one of the configs you're using currently? And check the logs to see if you see error or reboots, crashes, and/or if the LTE interface is having any issues (e.g. before getting to the ethernet port).

/interface bridge
add admin-mac=74:4D:28:9F:F7:93 auto-mac=no comment=defconf name=bridge
/interface lte
set [ find ] allow-roaming=no band="" name=lte1
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX disabled=no frequency=auto installation=outdoor mode=\
ap-bridge ssid=MikroTik-9FF794 wireless-protocol=802.11
/interface list
add name=WAN
add name=LAN
/interface lte apn
set [ find default=yes ] apn=fast.t-mobile.com use-network-apn=no
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.88.88-192.168.88.188
/ip dhcp-server
add address-pool=dhcp interface=bridge name=dhcp1
/port
set 0 name=serial0
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add interface=wlan1 list=LAN
add interface=lte1 list=WAN
add interface=bridge list=LAN
/ip address
add address=192.168.88.1/24 interface=bridge network=192.168.88.0
/ip dhcp-client
add comment=defconf interface=bridge
/ip dhcp-server network
add address=0.0.0.0/24 gateway=0.0.0.0 netmask=24
add address=192.168.88.0/24 gateway=192.168.88.1 netmask=24
/ip firewall filter
add action=accept chain=input protocol=icmp
add action=accept chain=input connection-state=established
add action=accept chain=input connection-state=related
add action=drop chain=input in-interface-list=!LAN
/ip firewall mangle
add action=change-ttl chain=postrouting new-ttl=set:65 passthrough=yes
/ip firewall nat
add action=masquerade chain=srcnat out-interface-list=WAN
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=bridge type=internal
add interface=lte1 type=external
/system clock
set time-zone-name=America/Chicago
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
[admin@MikroTik] >

Posted: **Tue Apr 12, 2022 1:39 am**

You might try deleting an extra IP/dhcp—server/network that quickset must have created:

/ip dhcp-server network
add address=0.0.0.0/24 gateway=0.0.0.0

Should not be there. You can safely delete it. Not sure that explain port drops.

Other than that your config looks like it should have LTE internet on WiFi or Ethernet1…

Posted: **Tue Apr 12, 2022 5:12 am**

You might try deleting an extra IP/dhcp—server/network that quickset must have created:
Code: Select all
/ip dhcp-server network
add address=0.0.0.0/24 gateway=0.0.0.0 
Should not be there. You can safely delete it. Not sure that explain port drops.

Other than that your config looks like it should have LTE internet on WiFi or Ethernet1…

Release and renew of my PC NIC fixes getting internet and so does Rebooting power to the Router I plug into the LtAP - just had not seen that needed on my other Tiks

Additionally it stays working until I try band 41 on the MODEM installed then all goes to pot. I lose the LTE from quickset etc. Takes forever to tweak setting to get it back.... I have a serious love/hate relationship with the LtAP LOL.
So I'm stable, I won't try band 41 for a while or at least I better get that looked at.
Just got a shipment of EM160 MODEMs so maybe that will be better than the EM12g

Posted: **Sun Apr 17, 2022 11:48 am**

I'd also recommend trying 7.2. It has a lot of LTE fixes over any of the 7.1.x versions.

Updating an LTAP on 7.2.1, the ROS update was successful
When i updated the firmware, the device lost the lte interface, i had to reboot it a second time in order to find it...

MikroTik

LtAP setup issues with LTE

LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE

Re: LtAP setup issues with LTE [SOLVED]