I have lowered the mtu of the lte interface (first lowered to 1942, then as low as 1360) but apparently that did not solve the problem.
Something else is happening here, I just don't know what. Tried to debug lte:
Code: Select all
/system logging
add topics=lte,debug
/log print follow
Here is a sample interface lte info (private ids hidden):
Code: Select all
pin-status: ok
registration-status: registered
functionality: full
manufacturer: "MikroTik"
model: "R11e-LTE"
revision: "MikroTik_CP_2.160.000_v015"
current-operator: Telekom HU
lac: 12345
current-cellid: 123456
enb-id: 1234
sector-id: 3
phy-cellid: 123
access-technology: Evolved 3G (LTE)
session-uptime: 3h54m43s
imei: 123456781234567
imsi: 123456781234567
uicc: 12345678123456781234
earfcn: 6350 (band 20, bandwidth 20Mhz)
rsrp: -72dBm
rsrq: -8dB
sinr: 23dB
cqi: 14
I can only access this device through ssh right now, I have no access to other computers on the LAN side. But here is a quick and dirty test that shows the connection problem on the router itself:
Code: Select all
[adm@router] > /system ssh [/resolve www.google.com] port=80
connectHandler: No route to host
Welcome back!
[adm@router] > /system ssh [/resolve www.google.com] port=80
connectHandler: No route to host
Welcome back!
[adm@router] > /system ssh [/resolve www.google.com] port=80
connectHandler: No route to host
Welcome back!
[adm@router] > /system ssh [/resolve www.google.com] port=80
connectHandler: No route to host
Welcome back!
[adm@router] > /system ssh [/resolve www.google.com] port=80
connectHandler: No route to host
Welcome back!
[user@router] > /system ssh [/resolve www.google.com] port=80
Welcome back!
[adm@router] >
Any idea what can cause this?
Thank you.