Hi,

I upgraded my LTE module. The status display shows that the Lte interface is running. How do I get it now that WiFi or Ethernet work or are connected to the Internet

Yu have to associate this with your DHCP client and WAN interface settings.
I dont use LTE so not sure.
The rest of the device works from default settings.................
Minor tweaking on wifi settings (SSID, security password etc..)

NEXT TIME CONTINUE WITH SAME ORIGINAL THREAD, I just noticed you already had one going.
For future reference.

pOst your config
/export hide-sensitive file=anynameyouwish

How can you connect the DHCP client to the WLAN interface?

Thanks for the tip..
I will implement

I now have orders
/ export hide-sensitive file = test

tried out. Where can I find the exported file?

I now have orders
/ export hide-sensitive file = test

tried out. Where can I find the exported file?

Hi there there should be no spaces between file equal sign or test, thus: file=test

It will be found under FILES

Thank you for your prompt reply. The file is in the attachment

(1) Why do you have two IP addresses for WLAN1 (suggesting removing the one in red)
/ip address
add address=192.168.88.1/24 comment=defconf interface=wlan1 network=\
192.168.88.0
add address=10.10.10.1/24 interface=wlan1 network=10.10.10.0

(2) Why do have have LAN setup that is also your WAN setup.
IS LTE your WAN connection or your LAN subnet. something is wrong here but since I dont understand LTE .

Can you draw a network diagram to show where internet is coming from and what your network looks like behind the mikrotik device?
Also state clearly what your expectations are for users or devices on your network.

[ so far I am guessing, is that you have an LTE capable router, that gets internet from a provider with a fixed private IP of 192.168.88.X, with gateway of 192.168.88.1]
But then you have no subnets for your own use no LAN?)

[1] Thank you, I deleted one address.

[2] I would like to access the Internet with the WAP-R using a SIM card. The router should then supply every connected device with the Internet via a LAN cable.

[3] How can I create a network diagram with Winbox? Unfortunately, I am not very familiar with Winbox.

[3] How can I create a network diagram with Winbox? Unfortunately, I am not very familiar with Winbox.

Easiest is papier and pencil and a picture

Hi there,

the functionality should look like this:

The configuration appears to be the default for a standard wAP with ether1 as the WAN and wlan1 as the LAN. I don't know if a reset to factory defaults would use a different configuration with the LTE modem being present, otherwise a few changes are needed:
/interface bridge
add name=bridge
/interface bridge port
add bridge=bridge interface=ether1
add bridge=bridge interface=wlan1
...
/ip dhcp-server
add address-pool=dhcp disabled=no interface=wlan1bridge name=defconf
...
/interface detect-internet
set detect-interface-list=WANnone internet-interface-list=allnone lan-interface-list=LANnone wan-interface-list=allnone
/interface list member
add comment=defconf interface=wlan1bridge list=LAN
add comment=defconf interface=ether1lte1 list=WAN
add list=LAN
...
/ip address
add address=192.168.88.1/24 comment=defconf interface=wlan1bridge network=192.168.88.0
add address=10.10.10.1/24 interface=wlan1 network=10.10.10.0
...
/ip route
add distance=1 gateway=192.168.88.1

When adding the bridge and bridge interfaces your Winbox session may get disconnected unless using a MAC rather than IP connection.

Also IIRC if you also need a DHCP client adding to acquire an address (as using passthough on a device here) which would be
/ip dhcp-client
add default-route-distance=1 disabled=no interface=lte1

(EDIT: already someone replied before me ... same lines of thinking)

The config you posted before, is that the default config of the device ?
The LTE + SIM card, is that your lte interface on your Mikrotik ?

I will also assume that you want to have AND Ethernet-clients AND wlan-clients as being part of LAN (= internal = 192.168.88.0/24 range).
Correct ?

Put eth1 on the LAN list, not WAN. Put lte-itf as WAN. Do this first and make sure to use Safe Mode when making this change since it can block your access if done wrong.
Your DHCP server is currently only serving wlan1 and I don't see a bridge where eth1 can be part of. If you add a bridge and put eth1 and wlan1 as part of that, change dhpc-server to bridge (which you will have to do anyhow since wlan1 will become a slave if you add it to the bridge)
I don't see a default route towards lte (and that definitely should be there): add route to 0.0.0.0/0, interface lte, distance 10 (I prefer to have the default path a bit out of the way, experts may disagree with that one)

I think that's the major part to have it working. Others will surely chime in.

To be honest, I'm still a little overwhelmed with the steps ..

At first I tried to implement the points mentioned below. Pictures in the attachment

Unfortunately, I don't know exactly how to implement these points:

Your DHCP server is currently only serving wlan1 and I don't see a bridge where eth1 can be part of. If you add a bridge and put eth1 and wlan1 as part of that, change dhpc-server to bridge (which you will have to do anyhow since wlan1 will become a slave if you add it to the bridge)
I don't see a default route towards lte (and that definitely should be there): add route to 0.0.0.0/0, interface lte, distance 10[/flash][/flash] (I prefer to have the default path a bit out of the way, experts may disagree with that one)

Post your lastest config !!

/export hide-sensitive file=anynameyouwish

As Anav said (without the exclamation marks )

On your lasts screenshots, the one for DHCP server: remove the line in red with defconf. It is invalid now because wlan1 is part of the bridge.
You can not run a DHCP server on a slave interface.

And then provide your export again please.

Thanks for the help

Attached the file

Unfortunately, I currently have the problem that the device sometimes does not want to connect to the PC

I didnt mean literally the file should be called anynameyouwish, I meant that you could use any name you desired for the file LOL

(1) Lets tidy this up.../interface list member
add comment=defconf interface=wlan1 list=LAN
add list=LAN
add interface=ether1 list=LAN
add interface=lte1 list=WAN..

TO
/interface list member
add comment=defconf interface=wlan1 list=LAN
add interface=ether1 list=LAN
add interface=lte1 list=WAN
add interface=eplus list=WAN {just to be sure we are capturing all possibilities as not familiar with LTE}

(2) From
/ip address
add address=192.168.88.1/24 comment=defconf interface=wlan1 network=\
192.168.88.0

TO
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
192.168.88.0

(3) Did you enter this IP route and if so why?? Typically we dont route to the gateway of the LAN but to the gateway of the WAN??
/ip route
add distance=1 gateway=192.168.88.1

Typically under either DHCP client or I suspect in your Case LTE client settings there is a selection for ADD DEFAULT ROUTE YES NO.

[1] Unfortunately I had problems with this point .. Picture in the attachment

The rest has worked so far. This time I even changed the name of the file: D

Do I have to add anything under the DHCP client?

I am not sure you need to frig with DHCP client, if you already have LTE client settings as a separate entity.
if you do need dhcp client then the interface would be the LTE one NOT the wifi one.

I am not sure you need to frig with DHCP client, if you already have LTE client settings as a separate entity.
if you do need dhcp client then the interface would be the LTE one NOT the wifi one.

No, it's not needed.
IP address should be provided through LTE interface.
Default route as well.

Interface for eplus is not needed either. Has nothing to do with Mikrotik interfaces.

Extract from my lte interface with a crucial part missing in red:
/interface lte apn
set [ find default=yes ] add-default-route=yes apn=xyz authentication=none \
default-route-distance=5 ip-type=ipv4 name=default use-network-apn=yes \
use-peer-dns=yes

You can find it here: Winbox - Interfaces - LTE - button LTE APN

I didnt mean literally the file should be called anynameyouwish, I meant that you could use any name you desired for the file LOL

Why not ? It's a name like any other.
Or would you prefer "becauseanavsaidso" ?

Thank you holvoetn ..

The box was already selected

Unfortunately I still have no internet

Did you reboot your device after all these changes ?
If that box was already ticked AND we still don't see a default address coupled to lte interface something is wrong.

Before you do:
Winbox - Files
Backup
"anynameyouwish" - don't encrypt (you can take care of that later if you want)
After creation, move that file to the flash part. That's the only way to have it survive a reboot (or move to disk, not all Mikrotik devices have that possibility)

Then reboot.

Other comment:
I do see you're still on an older version of ROS but that should not be a factor here.
For me authentication is set to NONE. I see you have PAP ? Can you also try to change that ?

I didnt mean literally the file should be called anynameyouwish, I meant that you could use any name you desired for the file LOL

Why not ? It's a name like any other.
Or would you prefer "becauseanavsaidso" ?

I prefer........... holvoshoulddriveavolvo

Why not ? It's a name like any other.
Or would you prefer "becauseanavsaidso" ?

I prefer........... holvoshoulddriveavolvo

Used to drive Audi. Now a Jag (never again. Other story ...).

Let's stay on topic here !!

@to55603
can you also provide screenshots of LTE interface - status and LTE interface - cellular ?

Drop the authentication comment.
It seems it has to be PAP for eplus. Just checked on their site.

and do include my suggestion
add interface=eplus list=WAN wont hurt if wrong will help immensely if right!!!

Did I forget any screenshots? Otherwise, just tell me on which page I should take screenshots or how I can get there

Step 1.
Clean up config remove the part in red and add blue

/interface list member
add comment=defconf interface=wlan1 list=LAN
add list=LAN
add interface=ether1 list=LAN
add interface=lte1 list=WAN
add interface=eplus list=WAN

/ip address
add address=192.168.88.1/24 comment=defconf interface=wlan1 network=\
192.168.88.0
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
192.168.88

FOR NOW Disable this rule, to ensure nothing is getting blocked.
/interface wireless access-list
add mac-address=CC:2F:71:A2:22:95


Finally try setting this to NONE for all.........,
/interface detect-internet
set detect-interface-list=WAN internet-interface-list=all lan-interface-list=\
LAN wan-interface-list=all

ALSO where are these coming from?? Delete them......
/ip route
add distance=1 gateway=192.168.88.1
add distance=1 gateway=192.168.88.1


Remove the static IP dns setting and not sure why you have some obscure dns server there so replace 159.... with 1.1.1.1 or 9.9.9.9
/ip dns
set allow-remote-requests=yes servers=159.148.60.2
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan

[1] At the first point I could not select the interface eplus. See Appendix

[2] With this part I unfortunately don't know where and how to do it;

Remove the static IP dns setting and not sure why you have some obscure dns server there so replace 159 .... with 1.1.1.1 or 9.9.9.9
/ ip dns
set allow-remote-requests = yes servers = 159.148.60.2
/ ip dns static
add address = 192.168.88.1 comment = defconf name = router.lan

Okay understand about eplus!

You need to go to IP DNS settings. Check Green rectangle...........
At the top you should see servers, and this is where I assume the 159 came in there, seems to be the fact that you stated use peer DNS, which is fine so that is why that is there,
do not remove it. You can add 1.1.1.1 for example as well.

To reach that static IP dns setting select the tag stating Static in Orange rectangle and then delete the entry.

Maybe basics first...
Does that SIM card work in another device ?
Because it should give an IP address on successful connection and I do not see it coming.

@anav
I implemented your tips. Many thanks for your help. I deleted the entry within the IP dns settings

@holvoetn
The SIM card was already running in another router. There were no problems with this

I still find it mighty strange there is no IP address for the lte interface, no default route, nada ...

From terminal, what does this give ?
/interface lte print

and

/interface lte info lte1 once

There is also no DHCP client. But it shouldn't be, that should come automatically.
However ... can you try this ?
/ip dhcp-client
add default-route-distance=5 disabled=no interface=lte1

And then /ip address print

These were the results:

Aha !
An IP address on LTE1 interface !!

What does /ip route show now ?

This is now displayed

Now we're talking !

You have a PC connected to LAN ? Does it get an IP address from WAP-R ?
Can it access internet ?

I have now connected the device to the PC via LAN. IP Config in the appendix. Unfortunately the PC indicates that the network cannot be identified

Other remark:
from that lte info lte1 once dump I see you're still on firmware V015.
Could be there is already a newer firmware available.

Check if new firmware is available for your device
/interface lte firmware-upgrade lte1

If so:
/interface lte firmware-upgrade lte1 upgrade=yes
And after success: reboot or /interface lte at-chat lte1 input="AT+reset"

Can you export your latest config again please ?
We're getting close.

The software should now be up to date ...

Strange, DHCP client on lte-interface is gone again ??
You did a reboot after the firmware upgrade ?
That DHPC setting has clearly not been saved ... hmmm ...

First reaction would be to do again:
/ip dhcp-client
add default-route-distance=5 disabled=no interface=lte1
See if IP address comes in on lte1 itf with /ip address

And something else: any reason why you're still on 6.46 for RouterOS ? That's a rather old version. If it works, ok, no reason to change but ... it might be needed HOWEVER the latest stable version seems to exhibit some boot-problems on some devices so I am hesitant to steer you into that direction. Let's try without upgrade first.

What version of Winbox are you using ?
Because I find it strange that the DHCP setting part does show in your Winbox screenshot but it's NOT visible in the export and you still need to set the DHCP-client manually.

Something else I am missing is the definition of your Ethernet interface... but how can it be connected to the bridge then ??
Is the eth1 interface visible in Winbox ? How is it setup ?

Are device able to connect through wifi ? Do they get an IP address from the router ?

Another thing:
ip dns set allow-remote-requests=yes -> Set to no !

Yes, I restarted the system again. I also tried again, but he seems to have a problem with the command add default-route-distance = 5 disabled = no interface = lte1 ..

Regarding the router version: I have not yet updated the router because I had problems with it at the beginning. That is why the original version is still on the device

I am currently using version 3.31 of Winbox

The problem with using the WAP-R later is that it is not connected directly to a PC. It is supposed to connect a circuit board to the Internet, with which a solar system can track the sun. Accordingly, it is best to only connect an Ethernet cable to the circuit board and to automatically assign the Internet via LAN

What confuses me is that the lTE seems to have a 10. xx address, the LAN is on 192.168.x.x
BUt the PC gets 169.254 ???

Regardless of the WAN situation the PC should simply get a proper LANIP from the router???

Ensure DNS setting is entered on this line.
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1

Should look like
/ip dhcp-server network
add address=192.168.88.0/24 dns-server=192.168.88.1 gateway=192.168.88.1

Also this is an interface, so
try to add either lte apn to the wan interface as a member and eplus

/interface lte apn
set [ find default=yes ] apn=internet.eplus.de authentication=pap name=eplus \
user=eplus

Can either be added below as a WAN member ( I know you tried eplus before but give it another stab and if not then try lte apn!!

/interface list member
add comment=defconf interface=wlan1 list=LAN
add interface=ether1 list=LAN
add interface=lte1 list=WAN

@to55603
Your last statement I sort of disagree. I also have a solar panel tracking system at home and it's nicely connected to my Wifi-network.
Just had to make sure to give it a fixed IP to be sure, that's all (open dynamic lease and make it static, as easy as that).
But could be your tracking system does not like Wifi that much (in 2021 ??)

Just realised (stupid me...): export does not show dynamic values.
Don't make screenshots, just copy-paste the output between [ code ] and [ / code] (without the spaces), much easier.

/interface ethernet print
/interface bridge port print
/ip address print
/ip route print
/ip dhcp-server lease print

The last screenshot you provided (ipconfig from PC) shows Drahtlos = WIRELESS (I understand a bit of German) ? But you said you were going to use a cable ?
It should not make a difference since wlan1 should also be connected to the bridge (which we will verify from the print-statements but from your Interface screenshot I see both eth1 and wlan1 with S for slave, so I think it's ok).
Therefor the DHCP-server for that bridge should hand out an IP address.

What confuses me is that the lTE seems to have a 10. xx address, the LAN is on 192.168.x.x
BUt the PC gets 169.254 ???

Regardless of the WAN situation the PC should simply get a proper LANIP from the router???

Makes perfect sense if the PC does not get a DHCP lease.
Then Windows will default to 169.254 range.
That's the problem which needs to be addressed now.

And the IP address for lte will most likely be a CGNAT address from the carrier.

Also this is an interface, so
try to add either lte apn to the wan interface as a member and eplus

/interface lte apn
set [ find default=yes ] apn=internet.eplus.de authentication=pap name=eplus \
user=eplus

Can either be added below as a WAN member ( I know you tried eplus before but give it another stab and if not then try lte apn!!

Doesn't work that way
The interface is called lte1 and it is included in the WAN list (it's visible in his latest export).

That's the result:

[admin@MikroTik] > /interface ethernet print
Flags: X - disabled, R - running, S - slave
# NAME MTU MAC-ADDRESS ARP SWITCH
0 RS ether1 1500 B8:69:F4:6A:3B:96 enabled switch1
[admin@MikroTik] > /interface bridge port print
Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload
# INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON
0 H ether1 bridge yes 1 0x80 10 10 none
1 wlan1 bridge 1 0x80 10 10 none
[admin@MikroTik] > /ip address print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK INTERFACE
0 ;;; defconf
192.168.88.1/24 192.168.88.0 bridge
1 D 10.128.157.147/32 10.128.157.147 lte1
[admin@MikroTik] > /ip route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADS 0.0.0.0/0 lte1 2
1 ADC 10.128.157.147/32 10.128.157.147 lte1 0
2 ADC 192.168.88.0/24 192.168.88.1 bridge 0
[admin@MikroTik] > /ip dhcp-server lease print
Flags: X - disabled, R - radius, D - dynamic, B - blocked
# ADDRESS MAC-ADDRESS HOST-NAME SERVER RATE-LIMIT STATUS LAST-SEEN

Unfortunately, this is the only solution for the circuit board ...

I am connected to the router via wifi, otherwise I cannot control it via Winbox. Or am I wrong?

Unfortunately, this is the only solution for the circuit board ...

No problem. I assume you will have looked into your options.

I am connected to the router via wifi, otherwise I cannot control it via Winbox. Or am I wrong?

Also here, no problem but I still don't get why your PC is not getting an IP lease. Are you connecting via Winbox and MAC-address ?

The circuit board is already connected via Ethernet ? It does not seem to get a lease either if it is.

No, not yet. The circuit board is permanently installed and I didn't want to remove the circuit board separately. Can I configure the whole system without the circuit board?

No, not yet. The circuit board is permanently installed and I didn't want to remove the circuit board separately. Can I configure the whole system without the circuit board?

Sure you can do it without the circuit board connected. It was just a question to be sure the ethernet client does not get a lease either.
Just for testing, can you confirm connecting your PC to the ethernet port ? It should NOT get a DHCP lease (nothing in the 192.168 range).
If it does, something might be wrong with the wifi-settings on your PC.

Oh and please:
/ip dns
set allow-remote-requests=yes

Set to no !

That's all

Hopefully I have now sent the correct part for the ethernet connection

[admin@MikroTik] > /ip dns
[admin@MikroTik] /ip dns> set allow-remote-requests=no
[admin@MikroTik] /ip dns> print
servers: 159.148.60.2,1.1.1.1
dynamic-servers: 62.109.121.17,62.109.121.18
allow-remote-requests: no
max-udp-packet-size: 4096
query-server-timeout: 2s
query-total-timeout: 10s
max-concurrent-queries: 100
max-concurrent-tcp-sessions: 20
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 21KiB

/interface bridge print
please ?

I am comparing your latest export with my config and your bridge looks REALLY simple.
Too simple.

Your config:
/interface bridge add name=bridge

Mine (I removed MAC address):
/interface bridge
add admin-mac=XX:XX:XX:XX:XX:XX ageing-time=5m arp=enabled arp-timeout=auto \
auto-mac=no comment=defconf dhcp-snooping=no disabled=no fast-forward=yes \
forward-delay=15s igmp-snooping=no max-message-age=20s mtu=auto name=\
bridge priority=0x8000 protocol-mode=rstp transmit-hold-count=6 \
vlan-filtering=no

Seems to be odd AND DHCP-client AND default bridge settings are missing on that device.
You may want to consider upgrading RouterOS later on.

I have now updated the router to 6.49. Hope it's the correct stable version. Definitely looks better now

[admin@MikroTik] > /interface bridge add name=bridge
failure: already have interface with such name
[admin@MikroTik] > /interface bridge
[admin@MikroTik] /interface bridge> print
Flags: X - disabled, R - running
0 R name="bridge" mtu=auto actual-mtu=1500 l2mtu=1598 arp=enabled arp-timeout=auto mac-address=XX:XX:XX:XX:XX:XX protocol-mode=rstp fast-forward=yes igmp-snooping=no auto-mac=yes ageing-time=5m priority=0x8000 max-message-age=20s forward-delay=15s
transmit-hold-count=6 vlan-filtering=no dhcp-snooping=no
[admin@MikroTik] /interface bridge>

I hope you changed that MAC address yourself and it was not set like that ?
Still no IP address on PC ?

Haha no
I changed the IP address myself

Unidentified network

There has to be something rather stupid preventing DHCP from handing out IP leases ...
It's the only thing missing.

Hmmm. Do you have any idea?

Yes the R in the title means both Holvo and I are Retar...... for not figuring this out.

Okok, how should I proceed now? Is there any solution to the problem at all

Okok, how should I proceed now? Is there any solution to the problem at all

Final export with all latest settings please.
/export verbose hide-sensitive file=youknowthedrill

Ok, here it is:

Wild idea (it has caused me some troubles already in the past as well, it just popped in):
what is the current time on your device ? How off is it from the real time ?

Because I do not see any setting on your device which would sync time with whatever.
And if the time difference is too much, I have seen clients reject DHCP leases and the other way around, DHCP server rejecting DHCP-requests.
On every device I have (Mikrotik, NAS, printer, PC, whatever) it's usually one of the first things I configure to get the time right.

Just to try:
/system ntp client
set enabled=yes
/system ntp client servers
add address=94.224.67.24
(IP address is for be.pool.ntp.org. You're in the same timezone as me if you're in Germany so don't worry)

Can you also provide the last 20-30 lines of log:
/log print (just enter til it's finished, then copy the last 20 or so lines)

BTW LOOOVE the way you simply copy-paste the names for the exports

Unfortunately, I had problems with the second command...

[admin@MikroTik] /system ntp client> /system ntp client servers
bad command name servers (line 1 column 20)
[admin@MikroTik] /system ntp client> add address=94.224.67.24
bad command name add (line 1 column 1)
[admin@MikroTik] /system ntp client> print
enabled: yes
primary-ntp: 0.0.0.0
secondary-ntp: 0.0.0.0
server-dns-names:
mode: broadcast
[admin@MikroTik] /system ntp client> /
[admin@MikroTik] > /log print
19:04:00 system,error,critical router was rebooted without proper shutdown
19:04:02 bridge,info "bridge" mac address changed to B8:69:F4:6A:3B:97
19:04:07 wireless,info CC:2F:71:A2:22:95@wlan1: connected, signal strength -55
19:04:09 bridge,info hardware offloading activated on bridge "bridge" ports: ether1
19:04:12 interface,info ether1 link up (speed 10M, full duplex)
19:04:14 interface,info ether1 link down
19:04:15 interface,info ether1 link up (speed 100M, full duplex)
19:04:24 lte,info lte1: registered home
19:04:25 interface,info lte1 link up
19:04:25 interface,info lte1 detect UNKNOWN
19:04:31 interface,info lte1 detect WAN
19:04:31 system,info,account user admin logged in from 54:E1:AD:74:CD:D9 via winbox
19:07:13 system,info package channel changed by admin
19:07:15 system,info package channel changed by admin
19:07:37 system,info,account user admin logged in via local
19:09:02 wireless,info CC:2F:71:A2:22:95@wlan1: disconnected, received deauth: unspecified (1), signal strength -53
21:12:09 wireless,info CC:2F:71:A2:22:95@wlan1: connected, signal strength -48
21:12:13 system,info,account user admin logged out from 54:E1:AD:74:CD:D9 via winbox
21:12:13 system,info,account user admin logged out via local
21:12:32 system,info,account user admin logged in from 54:E1:AD:74:CD:D9 via winbox
21:12:33 system,info,account user admin logged in via local
21:13:05 wireless,info CC:2F:71:A2:22:95@wlan1: disconnected, received deauth: unspecified (1), signal strength -48
21:13:06 system,info,account user admin logged out from 54:E1:AD:74:CD:D9 via winbox
21:13:06 system,info,account user admin logged out via local
21:33:35 wireless,info CC:2F:71:A2:22:95@wlan1: connected, signal strength -54
21:34:01 system,info,account user admin logged in from 54:E1:AD:74:CD:D9 via winbox
21:34:02 system,info,account user admin logged in via local
21:34:20 system,info SNTP client configuration changed by admin

Haha in Germany we say: The engineer is lazy

DHCP-client seems to be missing again on lte1 interface ?
Can you check /ip addresses print ?

In the last export, there is disabled=yes on the /ip dhcp-server row. Change that to disable=no.

And do not attempt to attach a dhcp client to the LTE interface, it is not necessary.

Also, under /interface detect-internet, set all the lists to none. That feature only causes headache.

In the last export, there is disabled=yes on the /ip dhcp-server row. Change that to disable=no.

And do not attempt to attach a dhcp client to the LTE interface, it is not necessary.

Good catch on the DHCP-server !

Re: dhcp-client:
I do agree it is not needed normally (it's not needed on my SXT LTE device) but there are LTE devices where it has to be done.
And from what I read left and right, WAP-R is one of them for some reason.
Before the upgrade, we could only get the external internet working after adding DHCP-client.

Could be this is not needed anymore after upgrade to 6.49.

How do I set / interfaceDetect-Internet to none?

And how do I change / ip dhcp-server to disable = no?

Unfortunately, Winbox is difficult to understand ...

1) Winbox - interfaces - there is a button "detect Internet". Open it and set everything to none.
2) Winbox - IP - DHCP-server - tab DHCP. Most likely there is a grayed line. Select it and make it active (blue tick mark on top)

Or
.. ....

I've tried it again now. I finally have internet through the device. Thank you so much both of you

Yeah !!

<High Five to anav and sindy!>

So what was the key, something previous before dhcp server was turned off, or the removal of detect internet