Community discussions

MikroTik App
 
GrumpyGiantbe
just joined
Topic Author
Posts: 5
Joined: Tue Oct 19, 2021 3:19 pm
Location: Belgium formerly known as the hell hole

LTE modme Connection problem

Sat Jan 01, 2022 9:40 pm

Hello all

I have a strange annoying problem with RBwAPGR-5HacD2HnD and R11e-LTE. The LTE interface play's hide and seek with me.
A few days ago the config was working for more then 48 hours. Afterwards the LTE interface disappears from the interface list. After a while it comes back online for 5-10 seconds.
I also already added the LTE interface tot the sys-log and it is constantly retrying to enable.
Here the sys-log below the sys-log there is also a config (a newbee but ain't my first rodeo).
18:33:48 lte,async lte1: sent AT E0 V1 
18:33:48 lte,async lte1: rcvd OK 
18:33:48 lte,async lte1: sent AT+CGMI 
18:33:48 lte,async lte1: rcvd +CGMI: "MikroTik" 
18:33:48 lte,async lte1: sent AT+CGMM 
18:33:48 lte,async lte1: rcvd +CGMM: "R11e-LTE" 
18:33:48 lte,async lte1: sent AT+CGMR 
18:33:48 lte,async lte1: rcvd +CGMR: "MikroTik_CP_2.160.000_v018" 
18:33:48 lte,async lte1: sent AT+CGSN 
18:33:48 lte,async lte1: rcvd +CGSN: 355654093753262 
18:33:48 lte,async lte1: sent AT+CFUN? 
18:33:48 lte,async lte1: rcvd +CFUN: 1 
18:33:48 lte,async lte1: sent AT+CFUN=4 
18:34:18 lte,async lte1: sent AT E0 V1 
18:34:18 lte,async lte1: rcvd OK 
18:34:18 lte,async lte1: sent AT+CGMI 
18:34:18 lte,async lte1: rcvd +CGMI: "MikroTik" 
18:34:18 lte,async lte1: sent AT+CGMM 
18:34:18 lte,async lte1: rcvd +CGMM: "R11e-LTE" 
18:34:18 lte,async lte1: sent AT+CGMR 
18:34:18 lte,async lte1: rcvd +CGMR: "MikroTik_CP_2.160.000_v018" 
18:34:18 lte,async lte1: sent AT+CGSN 
18:34:18 lte,async lte1: rcvd +CGSN: 355654093753262 
18:34:18 lte,async lte1: sent AT+CFUN? 
18:34:18 lte,async lte1: rcvd +CFUN: 1 
18:34:18 lte,async lte1: sent AT+CFUN=4 
18:34:52 lte,async lte1: sent AT E0 V1 
18:34:52 lte,async lte1: rcvd OK 
18:34:52 lte,async lte1: sent AT+CGMI 
18:34:52 lte,async lte1: rcvd +CGMI: "MikroTik" 
18:34:52 lte,async lte1: sent AT+CGMM 
18:34:52 lte,async lte1: rcvd +CGMM: "R11e-LTE" 
18:34:52 lte,async lte1: sent AT+CGMR 
18:34:52 lte,async lte1: rcvd +CGMR: "MikroTik_CP_2.160.000_v018" 
18:34:52 lte,async lte1: sent AT+CGSN 
18:34:52 lte,async lte1: rcvd +CGSN: 355654093753262 
18:34:52 lte,async lte1: sent AT+CFUN? 
18:34:52 lte,async lte1: rcvd +CFUN: 1 
18:34:52 lte,async lte1: sent AT+CFUN=418:33:48 lte,async lte1: sent AT E0 V1 
18:33:48 lte,async lte1: rcvd OK 
18:33:48 lte,async lte1: sent AT+CGMI 
18:33:48 lte,async lte1: rcvd +CGMI: "MikroTik" 
18:33:48 lte,async lte1: sent AT+CGMM 
18:33:48 lte,async lte1: rcvd +CGMM: "R11e-LTE" 
18:33:48 lte,async lte1: sent AT+CGMR 
18:33:48 lte,async lte1: rcvd +CGMR: "MikroTik_CP_2.160.000_v018" 
18:33:48 lte,async lte1: sent AT+CGSN 
18:33:48 lte,async lte1: rcvd +CGSN: 355654093753262 
18:33:48 lte,async lte1: sent AT+CFUN? 
18:33:48 lte,async lte1: rcvd +CFUN: 1 
18:33:48 lte,async lte1: sent AT+CFUN=4 
18:34:18 lte,async lte1: sent AT E0 V1 
18:34:18 lte,async lte1: rcvd OK 
18:34:18 lte,async lte1: sent AT+CGMI 
18:34:18 lte,async lte1: rcvd +CGMI: "MikroTik" 
18:34:18 lte,async lte1: sent AT+CGMM 
18:34:18 lte,async lte1: rcvd +CGMM: "R11e-LTE" 
18:34:18 lte,async lte1: sent AT+CGMR 
18:34:18 lte,async lte1: rcvd +CGMR: "MikroTik_CP_2.160.000_v018" 
18:34:18 lte,async lte1: sent AT+CGSN 
18:34:18 lte,async lte1: rcvd +CGSN: 355654093753262 
18:34:18 lte,async lte1: sent AT+CFUN? 
18:34:18 lte,async lte1: rcvd +CFUN: 1 
18:34:18 lte,async lte1: sent AT+CFUN=4 
18:34:52 lte,async lte1: sent AT E0 V1 
18:34:52 lte,async lte1: rcvd OK 
18:34:52 lte,async lte1: sent AT+CGMI 
18:34:52 lte,async lte1: rcvd +CGMI: "MikroTik" 
18:34:52 lte,async lte1: sent AT+CGMM 
18:34:52 lte,async lte1: rcvd +CGMM: "R11e-LTE" 
18:34:52 lte,async lte1: sent AT+CGMR 
18:34:52 lte,async lte1: rcvd +CGMR: "MikroTik_CP_2.160.000_v018" 
18:34:52 lte,async lte1: sent AT+CGSN 
18:34:52 lte,async lte1: rcvd +CGSN: 355654093753262 
18:34:52 lte,async lte1: sent AT+CFUN? 
18:34:52 lte,async lte1: rcvd +CFUN: 1 
18:34:52 lte,async lte1: sent AT+CFUN=4
Config
Might look funky but there was a reason for the madness. One port is for a LAN network to host an outdoor WiFi network. The ETH2 goes to a separate device that needs an LTE connection.
If there are suggestion for that config they are more than welcome.
# dec/31/2021 18:54:07 by RouterOS 6.49
# software id = FNHE-ES67
#
# model = RBwAPGR-5HacD2HnD
# serial number = E1770DC98D10
/interface bridge
add admin-mac=08:55:31:DB:C4:BB auto-mac=no comment=defconf name=bridge
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX disabled=no distance=indoors frequency=auto installation=outdoor mode=ap-bridge ssid=MikroTik-DBC4BD wireless-protocol=802.11
set [ find default-name=wlan2 ] band=5ghz-a/n/ac channel-width=20/40/80mhz-XXXX disabled=no distance=indoors frequency=auto installation=outdoor mode=ap-bridge ssid=MikroTik-DBC4BE wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
add comment=defconf name=LAN2
/interface lte apn
set [ find default=yes ] apn=telenetwap.be
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=Sim_Backhaul_Pool ranges=10.24.0.5-10.24.0.6
/ip dhcp-server
add address-pool=Sim_Backhaul_Pool bootp-support=none disabled=no interface=ether2 name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=wlan1
add bridge=bridge comment=defconf interface=wlan2
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf list=WAN
add comment=defconf interface=ether2 list=LAN2
/ip address
add address=10.10.10.0/16 comment=defconf interface=bridge network=10.10.0.0
add address=10.24.0.1/29 interface=ether2 network=10.24.0.0
/ip dhcp-server network
add address=10.24.0.0/29 dns-server=10.24.0.1,1.1.1.1 gateway=10.24.0.1 netmask=29
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
/system clock
set time-zone-name=Europe/Brussels
/system logging
add topics=lte,!raw
/system package update
set channel=long-term
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Hopefully somebody can help me out of my misery by either giving me a solution or telling me I am royally screwed.
Either one is fine by me but I hope for a solution.

Sincerely
a Grumpy Giant from Belgium
 
GrumpyGiantbe
just joined
Topic Author
Posts: 5
Joined: Tue Oct 19, 2021 3:19 pm
Location: Belgium formerly known as the hell hole

Re: LTE modme Connection problem  [SOLVED]

Tue Jan 04, 2022 11:43 am

I think I figured this one out.
I forgot to specify the bands that the LTE interface was allowed to use.
So for anyone wit the same problem my config is as follows:
(remember to specify a pin for the sim)
# jan/04/2022 10:39:50 by RouterOS 6.49
# software id = FNHE-ES67
#
# model = RBwAPGR-5HacD2HnD
# serial number = E1770DC98D10
/interface bridge
add admin-mac=08:55:31:DB:C4:BB auto-mac=no comment=defconf name=bridge
/interface lte
set [ find ] allow-roaming=yes band=1,3,7,20,8,2,38,40 name=lte1
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX distance=indoors frequency=auto installation=outdoor mode=ap-bridge ssid=MikroTik-DBC4BD wireless-protocol=802.11
set [ find default-name=wlan2 ] band=5ghz-a/n/ac channel-width=20/40/80mhz-XXXX distance=indoors frequency=auto installation=outdoor mode=ap-bridge ssid=MikroTik-DBC4BE wireless-protocol=802.11
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
add comment=defconf name=LAN2
/interface lte apn
set [ find default=yes ] apn=telenetwap.be
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=Sim_Backhaul_Pool ranges=10.24.0.5-10.24.0.6
/ip dhcp-server
add address-pool=Sim_Backhaul_Pool bootp-support=none disabled=no interface=ether2 name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=wlan1
add bridge=bridge comment=defconf interface=wlan2
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface detect-internet
set detect-interface-list=all
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=lte1 list=WAN
add comment=defconf interface=ether2 list=LAN2
/ip address
add address=10.10.10.0/16 comment=defconf interface=bridge network=10.10.0.0
add address=10.24.0.1/29 interface=ether2 network=10.24.0.0
/ip dhcp-server network
add address=10.24.0.0/29 dns-server=10.24.0.1,1.1.1.1 gateway=10.24.0.1 netmask=29
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
/system clock
set time-zone-name=Europe/Brussels
/system logging
add topics=lte,!raw
/system package update
set channel=long-term
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Sincerely
GG
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3254
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: LTE modme Connection problem

Tue Jan 04, 2022 5:26 pm

Interesting. It really shouldn't have dropped to modem to select a new channel - normally these are pretty seamless. But locking bands to only available one is really good idea anyway – apparently even better one than I thought since the interface shouldn't go away when you don't lock them.

Probably have, but you might want to check your firmware and make sure it's update to date. There is a option to do this in winbox on the LTE interface.
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1275
Joined: Tue Jun 23, 2015 2:35 pm

Re: LTE modme Connection problem

Mon Sep 25, 2023 3:56 am

i'm experiencing the same issue and your solution @GrumpyGiantbe didn't help me.

im can see Pin_Status=ERROR

@Amm0 i need your thoughts.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3254
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: LTE modme Connection problem

Mon Sep 25, 2023 7:16 am

i'm experiencing the same issue and your solution @GrumpyGiantbe didn't help me.
im can see Pin_Status=ERROR
Well that's a different problem ;).
Everything, including boot and LTE firmware, upgraded? See viewtopic.php?t=199087&hilit=B66#p1025119

Some questions:
Do you actually have a PIN on your SIM?
Other thing is try selecting ONLY "LTE" as the network type (e.g. uncheck 3G/GSM/etc)
Does this only happen if your specify "bands" to use? If you remove the band selection, does the error go away?
I generally start with the software...But it could also be a bad SIM, especially if outdoors. Try re-seating or putting tape on back to make it "thicker" to press better on the the pins.
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1275
Joined: Tue Jun 23, 2015 2:35 pm

Re: LTE modme Connection problem

Mon Sep 25, 2023 7:52 am

i'll get someone on site and do everything from zero

Thanks @Ammo

Who is online

Users browsing this forum: No registered users and 23 guests